ViewVC Help

View File | Revision Log | Show Annotations | Revision Graph | Root Listing

root/i-scream/projects/cms/documentation/minutes/minutes-20001113b.txt

Comparing projects/cms/documentation/minutes/minutes-20001113b.txt (file contents):
Revision 1.2 by tdb, Wed Nov 15 00:19:49 2000 UTC vs.
Revision 1.5 by tdb, Wed Nov 15 02:05:53 2000 UTC

#	Line 4 | Line 4 | Location: Eliot College, E3E room 8
4		Present: ajm4, tdb1
5		Absent: none
6
7	–	[tdb1: Documented by ajm4, comments added by tdb1.]
8	–
7		This meeting was between ajm4 and tdb1 to discuss and
8		possibly implement parts of the CORE and FilterManager
9		elements of the system.
#	Line 24 | Line 22 | to be a "funky" extra ;-)
22		[tdb1: this will also solve security issues with
23		unauthorised third parties changing settings.]
24
25	+	A standard has almost be devised for filenames of
26	+	configuration files. As it stands all hostname properties
27	+	will be get in a file with the following name;
28
29	+	hostname.domain.properties
30	+
31	+	nb. This will always be *lower case*. This is important as
32	+	some hosts (eg. stuE...) have mixed case, so having all
33	+	lower case saves confusion.
34	+
35	+	However, any other config files (such as the filterManager)
36	+	can have any name in any case. The file itself will be of
37	+	the name format;
38	+
39	+	name.properties
40	+
41	+	So in the case of the filterManager this would be
42	+	"filterManager.properties".
43	+
44	+	A standard should be defined here for concistency.
45	+
46		Next point was whether or not we would support elements
47		being able to be updated without restarting them, ie. a host
48		would be able to detect its configuration has changed and
#	Line 44 | Line 62 | methods:
62		where thus implemented and the configurator test class
63		modified to include a test of this system.
64
65	<	[tdb1: it was also noted at this stage that a java 'long' is
66	<	infact an IDL 'long long'.]
65	>	It should also be noted at this stage that a java 'long' is
66	>	defined as a 'long long' in the IDL->Java mapping.
67
68
69		The next item discussed was the CORBA IDL and general system
#	Line 76 | Line 94 | a HostInit object to handle this intialisation.  The f
94		thing a Host does is obtain its configuration, this is done
95		by the HostInit object obtaining the configuration of the
96		host on its behalf.  An initial protocol of how this system
97	<	works is as follows:
97	>	works is as follows (of course this is subject to later
98	>	alteration, but seemed like a "good idea at the time"):
99
81	–	[tdb1: This is of course subject to alteration, but at the
82	–	time it seemed like a "good idea".]
83	–
100		Host                    FilterManager.HostInit
101		STARTCONFIG ->
102		<- OK | ERROR
#	Line 94 | Line 110 | Host                    FilterManager.HostInit
110		ENDCONFIG ->
111		<- OK
112
113	+	If there is an ERROR returned after STARTCONFIG, this
114	+	indicates to the Host that there is no configuration
115	+	available for it at this time.  It may be possible to
116	+	continue using default values, but this is up to the host
117	+	configuration.  Again, this is not a certain feature and
118	+	should be discussed with other members of the group.
119	+
120		If the property section returns an ERROR then this indicates
121		to the host that that property requested doesn't exist, the
122		Host will then deal with this either by ending with an error
123		on the local system or by ignoring it if it can.
124
125	<	[tdb1: An ERROR after STARTCONFIG indicates no configuration
103	<	is available at all (ie. no file found).]
125	>	The above features were implemented.
126
105	–	The above features where implemented.
127
128	+
129		The next item needed to be developed is an architecture for
130		FilterParent's and FilterChild's, as the next stage of Host
131	<	initialisation is to be passed a reference to a FilterChild.
131	>	initialisation is to be passed a 'reference' to a
132	>	FilterChild.  This 'reference' will be a server and a port
133	>	and not a reference in the CORBA or Java way of thinking.
134
111	–	[tdb1: "passed a reference" will mean a server and a port,
112	–	not to be confused with Java or CORBA references.]
113	–
135		It was noted that on a "heart beat" with the system, a Host
136		should check to see if its configuration has changed.  If it
137		has it should then re-initialise itself.  This will allow
#	Line 128 | Line 149 | Host program itself.
149
150
151		All code generated was placed in the "experimental" tree of
152	<	CVS, awaiting approval from other group members.
152	>	CVS, awaiting approval from other group members.  It should
153	>	also be noted that although CVS records tdb1 as the
154	>	'checker inner', it was infact ajm4...as he was the king of
155	>	code during this meeting ;-p
156
157		Many small bug fixes were made to the existing code.
158
159		It was also noted that there is a need for coding standards.
160
161		As we had reached an appropriate stage to end, and given the
162	<	late hour, it was decided to conclude the meeting.
162	>	late hour, it was decided to conclude the meeting.  It was,
163	>	after all, nearly 7 hours of coding ;-)
164
165	<	[tdb1: It was, afterall, nearly 7 hours coding !]
165	>	Since this meeting took place tdb1 has produced Makefiles
166	>	to allow easy compiling and configuration of the code.
167
142	–	[tdb1: As a post-meeting effort Makefile's were constructed
143	–	to allow easy compiling and configuration of code.]
168
169		Meeting was concluded @ 20:45. Next meeting booked for 11:00
170		on Wednesday, until 12:30. Meeting with iau @ 13:30 on that

Diff Legend

–	Removed lines
+	Added lines
<	Changed lines
>	Changed lines