documentation/minutes/minutes-20001030.txt

Minutes of Meeting, 30/10/2000 @ 10:20
Location: UKC Computer Science Meeting Room

Present: ab11, ajm4, tdb1
Absent: pjm2

Absentee(s): Unable to attend due to weather conditions.

The intention of the meeting was to complete the Time Plan
Allocation, which is a required deliverable. Although almost
finished tasks had not been allocated to group members.

Tim noted that a soft reboot of Compsoc1 may be required to
enable the meeting to proceed as planned. Compsoc1 quietens
down.

A discussion about the sizes of compiled C++ programs on
Solaris concluded that the actual size of the binary 
executable is down to the setup of the compiler on the
target machine. It is decided that we should not worry 
about this hurdle until further into the projects 
development.

The technologies which the project would utilise were
discussed and the following points raised.

- During the first few phases of the development our own
  protocol should be used for communication between Hosts
  and server, and server and clients. If a defined
  technology, such as SNMP, is decided upon then this can
  easily be substituted in due to the modular design of the 
  applications.

- The protocol should be based on XML or a system not too 
  dis-similar. The reason for this is it all text based and
  thus easier to process.
  
- The use of UDP and TCP/IP as communication layers between
  hosts and filer/collectors. To be discussed further with
  possible input from JC and PSSC.
  
The use of heart beats was also discussed. It was decided 
that further thought would have to be given to the
implication of these before they would be finalised.

Meeting concluded @ 12:00pm  

Meeting re-conviened @ 3:00pm

Discussion on the implemention of the plugin technology 
concluded that data should flow through plugins in a 
sequential manner and should remain as plain text at all 
times. It was also discussed that plugins should have a 
'order' coded into them, to allow the data to flow in a 
suitable manner for the plugins.

Meeting concluded @ 4:30pm
Revision:	1.2
Committed:	Wed Nov 1 00:12:26 2000 UTC (24 years ago) by tdb
Content type:	text/plain
Branch:	MAIN
Changes since 1.1:	+13 -12 lines
Log Message:	A couple of lines went over 60 chars - now fixed.
#	User	Rev	Content
1	ab11	1.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 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	tdb	1.2	Solaris concluded that the actual size of the binary
19	ab11	1.1	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	tdb	1.2	The technologies which the project would utilise were
25	ab11	1.1	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	tdb	1.2	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	ab11	1.1
34			- The protocol should be based on XML or a system not too
35	tdb	1.2	dis-similar. The reason for this is it all text based and
36	ab11	1.1	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	tdb	1.2	that further thought would have to be given to the
44			implication of these before they would be finalised.
45	ab11	1.1
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	tdb	1.2	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	ab11	1.1
57			Meeting concluded @ 4:30pm