Login Web Service Development

LL-3:  Login service now generates a random string for use as a session
id.  The id gets put into a hashmap as the key in the k/v pair with a
MySQL object being the value.  The MySQL object contains a connection to
the DB using the stored username/password credentials in a temporary
User object.  The session id is then wrapped into a cookie and appended
to the REST response in the login service, so that clients may identify
themselves on successive requests.

The cookie currently has no age/expiry setting, and the REST service
currently cannot check incoming cookies against the hashmap of active
sessions.