--- projects/cms/documentation/minutes/minutes-20001113b.txt	2000/11/15 00:19:49	1.2
+++ projects/cms/documentation/minutes/minutes-20001113b.txt	2000/11/15 00:33:45	1.3
@@ -44,8 +44,8 @@ methods: 
 where thus implemented and the configurator test class
 modified to include a test of this system.
 
-[tdb1: it was also noted at this stage that a java 'long' is 
-       infact an IDL 'long long'.]
+It should also be noted at this stage that a java 'long' is 
+defined as a 'long long' in the IDL->Java mapping.
 
 
 The next item discussed was the CORBA IDL and general system
@@ -76,11 +76,9 @@ a HostInit object to handle this intialisation.  The f
 thing a Host does is obtain its configuration, this is done
 by the HostInit object obtaining the configuration of the
 host on its behalf.  An initial protocol of how this system
-works is as follows:
+works is as follows (of course this is subject to later
+alteration, but seemed like a "good idea at the time"):
 
-[tdb1: This is of course subject to alteration, but at the 
-       time it seemed like a "good idea".]
-
 Host                    FilterManager.HostInit
     STARTCONFIG ->
                         <- OK | ERROR
@@ -94,23 +92,28 @@ Host                    FilterManager.HostInit
     ENDCONFIG ->
                         <- OK
 
+If there is an ERROR returned after STARTCONFIG, this
+indicates to the Host that there is no configuration 
+available for it at this time.  It may be possible to
+continue using default values, but this is up to the host
+configuration.  Again, this is not a certain feature and
+should be discussed with other members of the group.
+
 If the property section returns an ERROR then this indicates
 to the host that that property requested doesn't exist, the
 Host will then deal with this either by ending with an error
 on the local system or by ignoring it if it can.
 
-[tdb1: An ERROR after STARTCONFIG indicates no configuration 
-       is available at all (ie. no file found).]
+The above features were implemented.
 
-The above features where implemented.
 
+
 The next item needed to be developed is an architecture for
 FilterParent's and FilterChild's, as the next stage of Host 
-initialisation is to be passed a reference to a FilterChild.
+initialisation is to be passed a 'reference' to a
+FilterChild.  This 'reference' will be a server and a port
+and not a reference in the CORBA or Java way of thinking.
 
-[tdb1: "passed a reference" will mean a server and a port, 
-       not to be confused with Java or CORBA references.]
-
 It was noted that on a "heart beat" with the system, a Host
 should check to see if its configuration has changed.  If it
 has it should then re-initialise itself.  This will allow 
@@ -128,19 +131,22 @@ Host program itself.
 
 
 All code generated was placed in the "experimental" tree of
-CVS, awaiting approval from other group members.
+CVS, awaiting approval from other group members.  It should
+also be noted that although CVS records tdb1 as the 
+'checker inner', it was infact ajm4...as he was the king of
+code during this meeting ;-p
 
 Many small bug fixes were made to the existing code.
 
 It was also noted that there is a need for coding standards.
 
 As we had reached an appropriate stage to end, and given the
-late hour, it was decided to conclude the meeting.
+late hour, it was decided to conclude the meeting.  It was,
+after all, nearly 7 hours of coding ;-)
 
-[tdb1: It was, afterall, nearly 7 hours coding !]
+Since this meeting took place tdb1 has produced Makefiles
+to allow easy compiling and configuration of the code.
 
-[tdb1: As a post-meeting effort Makefile's were constructed 
-       to allow easy compiling and configuration of code.]
 
 Meeting was concluded @ 20:45. Next meeting booked for 11:00 
 on Wednesday, until 12:30. Meeting with iau @ 13:30 on that