2 - several files don't have version identifiers; a simple $Id in the
3 comment would help in finding packaging bugs. (Also recommended for
4 the documentation files)
5 - Most makefiles and stylesheets miss a copyright header.
8 - There is no reference to the gnucomo website in the manifest, design,
12 - A page with notification (independent of object) (with sort capabilities
13 and grouping per urgency). (PR 7)
14 - With an object one should be able to indicate what OS is being used
15 - Webpages should look more 'sexy'
16 - Draw graphs of DYNAMIC properties.
17 - Use XML/XSLT technology for the web interface.
19 - Edit the range of DYNAMIC properties for each parameter.
23 - Linking database users to objects (only certain objects can be shown to certain users)
27 - Make a proper master daemon for the Gnucomo server. This daemon handles
28 authorization of clients, scheduling and dispatching.
29 - The input filename for gcm_input can be a command argument. (PR 9)
30 - When gcm_input can not make a connection to the database, its input
31 message will be lost. In such a case, gcm_input should store the
32 message in a spool directory for a retry later on. (PR 10)
33 - Indicate to gcm_input what type of data is delivered (PR 11)
34 - Update statistics in the object table when a new parameter is entered
35 - Update statistics in the object table when a new notification is entered
39 - Build IP-database on the basis of whois
40 - Create mechanism for starting and ending the daemon.
41 - Performance check on the gnucomo-database
42 - Detect traces of log entries and use these traces to create notifications.
43 - Trend analysis of DYNAMIC properties.