Added communication static variables to include start of message, end of
message and message regex pattern.  Hopefully these are unique enough to
prevent collision with data.  Attempted to use STX and ETX, but STX was
either bugged with Java regex, sockets, Output/InputStream, or
reader/writer as I couldn't match on STX.  I used ETX on start and end
wih a combination of space and tab characters in a certain order, and
reversed that order for end of message.

Fixed a NPE when going from XML to Object on events, marshaller does not
pass logger so we were bombing there on deduplications.  I attempted to
add a set method for the logger, but JAXB was grabbing that method and
trying to add it even though there wasn't any notation on it.  I may
attempt to allow logger to pass somehow later.

Fleshed out ObjectatUser a bit and added ObjectatUserPermissions, which
is currenlty empty.  Not sure what method security will take yet,
focusing on input/output from Objectat at the moment.

Updated connection and listener to take input of a JAXBContext to reduce
memory/CPU usage on generating the context.  This context willbe passed
in from the main Objectat process once defined, currently the Test suite
pushes it in.

Performed further testing with synthetic events using Surface Pro (4GB
RAM and i5 processor).  Starting 9 XML event generators at 100 events
per second and 2 of those (200 events per second) being duplicated keys
we were pretty much pegged out on processor and RAM.  Objectat was at
around 600M RAM with 72K events and processor was at around 66% (overall
CPU ~97%).  Performance seems pretty good for its purpose at this point.
The chance of having 700 events per second and 200 duplicate events per
second is pretty extreme.  Especially a constant load with threads
running at a 10ms timer.  I'd expect feeds coming into the Objectat to
be separate systems in most cases, which would greatly reduce resource
consumption.  I would also expect usage of this app to be for a much
smaller scale, 900 events per second would be a huge number for most
cases.