Overall:
 - Makefiles, figure out platforms and mechanism for handling variances (uname -s ?)
 - Add information requesting and user searching
 - Create central server and directory functions for global searching

Server:
 Core
 - deal with the error-to on packet delivery
 - add client version to status=online updates?
 - timeout stale connections for clients and transports
 - logging
 - init - bind multiple addresses if configured
 - system generated messages in defines
 - on exit signal, try to deliver all packets left?
 Module
 - add module phase for handling errors
 - perl bindings?
 - basic one storing offline messages, sync data to file?
 - ISP module, instant setup, minimal configuration/features?  Maybe special ISP server?
 - MySQL feature filled module
 - Auth possibilities: db, passwd, IMAP, HTTP, ICQ, AIM, Radius... maybe as a sub-module of other main one?
 Transports
 - ICQ(13634234@ICQ)
 - AIM(Jo Bo Willie@AIM)
 - SMTP(user%host.com@EMAIL) maybe smart module can offer auto-try email when not a jabber user?
    Maybe: can natively deliver messages? deliver through sendmail? Native recieve incoming messages, or sendmail?
 - Native perl module for writing perl transports

Client:
 Lib
 - local system file-socket connection sharing
 - lib cache/stack of user status and incoming messages
 Commands
 - create command line apps that use local system shared file-socket

Future:
 Server
 - Move to an internal memory management model similiar to Apache
 - Threads
 - Replace certian functions to make system compatibility easier and safer, in part of internal memory management model?

