/[i-scream]/projects/cms/documentation/minutes/minutes-20001030.txt
ViewVC logotype

Contents of /projects/cms/documentation/minutes/minutes-20001030.txt

Parent Directory Parent Directory | Revision Log Revision Log | View Revision Graph Revision Graph


Revision 1.4 - (show annotations)
Mon Nov 6 19:11:29 2000 UTC (18 years, 6 months ago) by ab11
Branch: MAIN
CVS Tags: PROJECT_COMPLETION, HEAD
Changes since 1.3: +1 -1 lines
File MIME type: text/plain
Modified header

1 Minutes of Meeting, 30/10/2000 @ 10:20
2 Location: UKC Computer Science Meeting Room
3
4 Present: ab11, ajm4, tdb1
5 Absent: pjm2
6
7 Absentee(s): Unable to attend due to adverse weather conditions.
8
9 The intention of the meeting was to complete the Time Plan
10 Allocation, which is a required deliverable. Although almost
11 finished tasks had not been allocated to group members.
12
13 Tim noted that a soft reboot of Compsoc1 may be required to
14 enable the meeting to proceed as planned. Compsoc1 quietens
15 down.
16
17 A discussion about the sizes of compiled C++ programs on
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 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
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 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
39 hosts and filer/collectors. To be discussed further with
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
44 implication of these before they would be finalised.
45
46 Meeting concluded @ 12:00pm
47
48 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 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

  ViewVC Help
Powered by ViewVC 1.1.26