| 1 |
|
Minutes of Meeting, 13/11/2000 @ 14:00 |
| 2 |
< |
Location: Eliot College, room E3E |
| 2 |
> |
Location: Eliot College, E3E room 8 |
| 3 |
|
|
| 4 |
|
Present: ajm4, tdb1 |
| 5 |
|
Absent: none |
| 6 |
|
|
| 7 |
+ |
[tdb1: Documented by ajm4, comments added by tdb1.] |
| 8 |
+ |
|
| 9 |
|
This meeting was between ajm4 and tdb1 to discuss and |
| 10 |
|
possibly implement parts of the CORE and FilterManager |
| 11 |
|
elements of the system. |
| 21 |
|
isn't seen to be a real problem though, as it was only going |
| 22 |
|
to be a "funky" extra ;-) |
| 23 |
|
|
| 24 |
+ |
[tdb1: this will also solve security issues with |
| 25 |
+ |
unauthorised third parties changing settings.] |
| 26 |
+ |
|
| 27 |
+ |
|
| 28 |
|
Next point was whether or not we would support elements |
| 29 |
< |
being able to be updated without restarting them ie, a host |
| 29 |
> |
being able to be updated without restarting them, ie. a host |
| 30 |
|
would be able to detect its configuration has changed and |
| 31 |
|
adjust accordingly. The method chosen was to use the last |
| 32 |
|
modified date stamp of the configuration file as an |
| 38 |
|
configuration has been updated, and act accordingly. The |
| 39 |
|
methods: |
| 40 |
|
|
| 41 |
< |
long Configuration.getLastModifed() and |
| 42 |
< |
boolean Configurator.isModified(config) |
| 41 |
> |
long Configuration.getLastModifed() and |
| 42 |
> |
boolean Configurator.isModified(String conf, long curTime) |
| 43 |
|
|
| 44 |
|
where thus implemented and the configurator test class |
| 45 |
|
modified to include a test of this system. |
| 46 |
|
|
| 47 |
+ |
It should also be noted at this stage that a java 'long' is |
| 48 |
+ |
defined as a 'long long' in the IDL->Java mapping. |
| 49 |
|
|
| 50 |
|
|
| 51 |
|
The next item discussed was the CORBA IDL and general system |
| 75 |
|
a HostInit object to handle this intialisation. The first |
| 76 |
|
thing a Host does is obtain its configuration, this is done |
| 77 |
|
by the HostInit object obtaining the configuration of the |
| 78 |
< |
host its behalf. An initial protocol of how this system |
| 79 |
< |
works is as follows: |
| 78 |
> |
host on its behalf. An initial protocol of how this system |
| 79 |
> |
works is as follows (of course this is subject to later |
| 80 |
> |
alteration, but seemed like a "good idea at the time"): |
| 81 |
|
|
| 82 |
|
Host FilterManager.HostInit |
| 83 |
|
STARTCONFIG -> |
| 84 |
< |
<- OK | ERROR |
| 84 |
> |
<- OK | ERROR |
| 85 |
|
LASTMODIFIED -> |
| 86 |
< |
<- LASTMODIFIED |
| 86 |
> |
<- LASTMODIFIED |
| 87 |
|
DO { |
| 88 |
|
PROPERTY -> |
| 89 |
< |
<- VALUE | ERROR |
| 89 |
> |
<- VALUE | ERROR |
| 90 |
|
} UNTIL GOT CONFIG |
| 91 |
|
|
| 92 |
|
ENDCONFIG -> |
| 93 |
< |
<- OK |
| 93 |
> |
<- OK |
| 94 |
|
|
| 95 |
+ |
If there is an ERROR returned after STARTCONFIG, this |
| 96 |
+ |
indicates to the Host that there is no configuration |
| 97 |
+ |
available for it at this time. It may be possible to |
| 98 |
+ |
continue using default values, but this is up to the host |
| 99 |
+ |
configuration. Again, this is not a certain feature and |
| 100 |
+ |
should be discussed with other members of the group. |
| 101 |
+ |
|
| 102 |
|
If the property section returns an ERROR then this indicates |
| 103 |
|
to the host that that property requested doesn't exist, the |
| 104 |
|
Host will then deal with this either by ending with an error |
| 105 |
|
on the local system or by ignoring it if it can. |
| 106 |
|
|
| 107 |
< |
The above features where implemented. |
| 107 |
> |
The above features were implemented. |
| 108 |
|
|
| 109 |
+ |
|
| 110 |
+ |
|
| 111 |
|
The next item needed to be developed is an architecture for |
| 112 |
|
FilterParent's and FilterChild's, as the next stage of Host |
| 113 |
< |
initialisation is to be past a reference to a FilterChild. |
| 113 |
> |
initialisation is to be passed a 'reference' to a |
| 114 |
> |
FilterChild. This 'reference' will be a server and a port |
| 115 |
> |
and not a reference in the CORBA or Java way of thinking. |
| 116 |
|
|
| 117 |
|
It was noted that on a "heart beat" with the system, a Host |
| 118 |
|
should check to see if its configuration has changed. If it |
| 131 |
|
|
| 132 |
|
|
| 133 |
|
All code generated was placed in the "experimental" tree of |
| 134 |
< |
CVS, awaiting approval from other group members. |
| 134 |
> |
CVS, awaiting approval from other group members. It should |
| 135 |
> |
also be noted that although CVS records tdb1 as the |
| 136 |
> |
'checker inner', it was infact ajm4...as he was the king of |
| 137 |
> |
code during this meeting ;-p |
| 138 |
|
|
| 139 |
|
Many small bug fixes were made to the existing code. |
| 140 |
|
|
| 141 |
|
It was also noted that there is a need for coding standards. |
| 142 |
|
|
| 143 |
|
As we had reached an appropriate stage to end, and given the |
| 144 |
< |
late hour, it was decided to conclude the meeting. |
| 144 |
> |
late hour, it was decided to conclude the meeting. It was, |
| 145 |
> |
after all, nearly 7 hours of coding ;-) |
| 146 |
> |
|
| 147 |
> |
Since this meeting took place tdb1 has produced Makefiles |
| 148 |
> |
to allow easy compiling and configuration of the code. |
| 149 |
> |
|
| 150 |
|
|
| 151 |
|
Meeting was concluded @ 20:45. Next meeting booked for 11:00 |
| 152 |
|
on Wednesday, until 12:30. Meeting with iau @ 13:30 on that |
