==============================================================================
ACQUIRE:
------------------------------------------------------------------------------
1. Find a more secure client/server connection/protocol to push the logs 
    through.
2. Consider using 'live' feed to the server whenever connectivity will support
    it and then switch to an 'archival' mode otherwise.

==============================================================================
PARSE:
------------------------------------------------------------------------------
1. Clean up the monitoring/debugging message statements in the prepLogs4DBMS 
    scripts.
2. The code in 'prepLogs4DBMS_Main.pl' could probably be written more 
    concisely.
3. The organization of 'prepLogs4DBMS_Vars.pm' needs to be cleaned up.
4. Multilined log entries should be handled whether lines after the first are 
    indented or not.
5. The call to 'concatLines' in 'prepLogs4DBMS_DoSmbs.pm' should use parameters.
6. In 'prepLogs4DBMS_DoLogins.pm' the buffer files can (or should) be arrays in 
    memory.

==============================================================================
DBMS:
------------------------------------------------------------------------------
1. Allow update of date_time field only in main tables rather than inserting a 
    new record that will differ from other records only in the value of the 
    date_time field.
2. Clean up the monitoring/debugging message statements in the load_tables 
    script.
3. Find secure means of making RDMS usernames, passwords available to the 
    scripts.
4. Setup long term archiving database, schedule. MySQL supports compressed,
    read only tables.
5. Design the database to be the most efficient. 

==============================================================================
ANALYSIS:
------------------------------------------------------------------------------
1. Develop the scripts or httpd-dbms interface that will allow the 'right mix'
    of preset queries and 'ad-hoc' queries, i.e., develop the interface 
    between the httpd and the RDBMS.
2. Message editor: Allows "on-the-fly" parsing of message data in order to focus
    on only part of the message(s) or reduce redundancy. For example, removing
    pid's or elapsed time values from the messages when these are the only
    differences among the list of messages should reduce the number of 
    messages you have to deal with.

==============================================================================
HTTPD:
------------------------------------------------------------------------------
1. Develop the presentation of the Intranet Logger for Intranet/Internet
    consumption, i.e., the http access to the database.
2. Impose login restrictions.
3. Setup data mining interface.

==============================================================================
SECURITY:
------------------------------------------------------------------------------
1. Disaster recovery. What method should be in place to best facilitate 
    disaster recovery?

==============================================================================
GENERAL:
------------------------------------------------------------------------------
1. Accomodate other operating systems, environments, i.e., WinStuff, MacStuff, 
    other Unices, Linuces.
2. Port scripts to use other DBMS's (Oracle, Sybase, PostgreSQL, DB2 Linux, etc)
3. Port scripts to use other http daemons and/or scripting interfaces.
4. Variables throughout need to be re-evaluated in terms of where they are 
    declared, i.e., whether locally or in 'prepLogs4DBMS_Vars.pm'.
5. Put the documentation in dvi format.
6. Documentation. Presently most kindly described as being in a state of disarray.
    Consolidate it.
7. Get benchmarking data together.
8. Get a step by step setup together.