That should be all the interface changes needed for doing logouts
from the client.  Note that I'm not implementing the logic of a disconnect
in the database layers themselves -- they should only be getting invoked
via the X(ml)Msg layer from a client.  Everything, but EVERYTHING is
atomic operations, committed or rolled back individually.  Otherwise
database performance sucks most heinously.  Only in server-side code can
you do more than one operation within a beginTransaction/doCommit block.