[JDEV] Standards

[Jerrad Pierce]

>A client-side conf sounds good, but I see no reason to keep all that
>information client side and then have to develop *another* protocol
>interface for some custom roaming solution. Why not take advantage of the
>jabber design philosophy and keep client-conf serverside except for the
>essientals like hostname/port, username, password?
So yo're saying two files?
.jabber.vars which includes the account configurations (username, password,
server, port) and .jabber.clients? Both which have a standardized XML format
(clients can opt out of using them, but it is highly recommended not to)
And then clients get's pushed back up to the server via some <x>?
(say the client takes a fingerprint or time-stamp of the clients file on
start, and upon exit if it's changes push it up?)

(for win32 _jabber.vars _jabber.clients. or we could have a sub-directory of ~
.jabber/_jabber and then have vars and clients be files in it)