ViewVC Help
View File | Revision Log | Show Annotations | Revision Graph | Root Listing
root/i-scream/projects/cms/documentation/minutes/minutes-20001030.txt
(Generate patch)

Comparing projects/cms/documentation/minutes/minutes-20001030.txt (file contents):
Revision 1.1 by ab11, Tue Oct 31 14:50:17 2000 UTC vs.
Revision 1.3 by ab11, Mon Nov 6 18:15:11 2000 UTC

# Line 4 | Line 4 | Location: UKC Computer Science Meeting Room
4   Present: ab11, ajm4, tdb1
5   Absent: pjm2
6  
7 < Absentee(s): Unable to attend due to weather conditions.
7 > Absentee(s): Unable to attend due to lack of commitment.
8  
9   The intention of the meeting was to complete the Time Plan
10   Allocation, which is a required deliverable. Although almost
# Line 15 | Line 15 | enable the meeting to proceed as planned. Compsoc1 qui
15   down.
16  
17   A discussion about the sizes of compiled C++ programs on
18 < solaris concluded that the actual size of the binary
18 > Solaris concluded that the actual size of the binary
19   executable is down to the setup of the compiler on the
20   target machine. It is decided that we should not worry
21   about this hurdle until further into the projects
22   development.
23  
24 < The technologies which the project would ultilise were
24 > The technologies which the project would utilise were
25   discussed and the following points raised.
26  
27   - During the first few phases of the development our own
28    protocol should be used for communication between Hosts
29 <  and server, and server and clients. If a defined technology
30 <  such as SNMP is decided upon then this can easily be sub-
31 <  stituted in due to the modular design of the applications.
29 >  and server, and server and clients. If a defined
30 >  technology, such as SNMP, is decided upon then this can
31 >  easily be substituted in due to the modular design of the
32 >  applications.
33  
34   - The protocol should be based on XML or a system not too
35 <  dissimilar. The reason for this is it all text based and
35 >  dis-similar. The reason for this is it all text based and
36    thus easier to process.
37    
38   - The use of UDP and TCP/IP as communication layers between
# Line 39 | Line 40 | discussed and the following points raised.
40    possible input from JC and PSSC.
41    
42   The use of heart beats was also discussed. It was decided
43 < that further thought would have to be given to the implication
44 < of these before they would be finalised.
43 > that further thought would have to be given to the
44 > implication of these before they would be finalised.
45  
46   Meeting concluded @ 12:00pm  
47  
# Line 48 | Line 49 | Meeting re-conviened @ 3:00pm
49  
50   Discussion on the implemention of the plugin technology
51   concluded that data should flow through plugins in a
52 < sequental manner and should remain as plain text at all times.
53 < It was also discussed that plugins should have a 'order' coded
54 < into them, to allow the data to flow in a suitable manner for
55 < the plugins.
52 > sequential manner and should remain as plain text at all
53 > times. It was also discussed that plugins should have a
54 > 'order' coded into them, to allow the data to flow in a
55 > suitable manner for the plugins.
56  
57   Meeting concluded @ 4:30pm

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines