Last successful login is recorded

Code cleanup and commenting, along with fixing an oversight where the
last login date was not set
Fixed bug where only one message is recieved

Missed a line where the server then proceeds to listen for more incoming
data on that connection
Outline of server management

There is an extendable type for server messages, with a core class
controlling server connections. This will eventually be extended to
monitor servers and create new ones as needed.
Disconnects inactive servers from the cluster

A constant is defined stating the maximum number of seconds a server can
remain "connected" for without transferring data. If this time is
exceeded the socket is closed and the server is removed from the active
connections list. In addition a pulse message type has been added to
allow servers to remain connected even when there is no immediate need
for them.
Moved some networking code to a common library

Moved the message types to a common library in preparation for the
simulation server. Added the ZoneController class but it is currently
just a placeholder
Log system in place

A logging class is now in place and some of the default
console.writelines have been replaced with the log system. On exit the
log is saved to AWS Simple Storage Service.
Bug fixes with preceding commits

Fixed a comparison that resulted in the logger never being created

Changed form xml serialization to binary as Dictionary is not supported
by xml seriliazer

Added a temporary certificate for the ssl connection
Completed the metaverse logging so far

Changed the format so it use folders nicely
Added in several log events
Changed log fromate to include time as well date
Created a simple client

Created a simple wpf client application that connects to the server.
Also changed the ssl certificate to allow connection. However, sending
data does not work as a close event sends data
Modified connection to handle unexpected close

The connection has been changed to read the byte arrays and then
deserialize them using MemoryStream. This is a more elegant solution and
has the secondary benefit of when the stream is unexpectadly closed we
are able to handle this gracefully.
Messages transmit successfully from the client

Changed fom xml to binary serialization as this should be more efficient
and added the serializable attributes
Response messages are parsed, client can login

The system has been fully tested, and the authntication subsytem works
well. Users are able to be registered and logged in successfully using
the client.