2014.07.17 MSS Code Factory 1.11.12270 Added new interface and implementation for extended connect

An extended connect method has been added to the ISchemaSchemaObj and SchemaSchemaObj interface
and implementation which takes the cluster name, tenant name, and secuser name as arguments.  If a
connection to the database is established, this information is used to establish the authentication
for the session automatically, including the creation of a SecSession object.

Now that I've worked out what the method needs to access, I can proceed with defining the
request and response messages for a login.  I need to do that because even with a client-server
implementation, I'm relying on X(ml)Msg internally to enforce transactional interfaces on all
data access by the client.  This serves to dramatically improve the deployment scalability
of a client-server application, and provides testing of the code that would be deployed as
seperate client and server implementations bridged by an XML message transport.

Obviously in the long run I'll set up a Java Servlet interface to run the server, and use
a virtual web client API to issue the XML requests and receive the XML responses over an
SHTTP link.  (Probably just regular HTTP at first, which means it's a security hole from hell.)