[JDEV] Standards

[Peter Millard]

> Quoting Dave Smith <dsmith at ai.uwf.edu>:
> > 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?
>
>   That's my primary argument..

Keeping just connection info client side makes sense...
Assuming that we can send/recv all of the vcard stuff to/from the server using
the jabber:iq:info namespace. This should work well.

The only issues are client-specific options... many of these would need to be
read BEFORE the connection is established, and these are not likely to be useful
to other clients also. (IE, Cabber won't want to read WinJab's prefs..) So
really what we need to do is to really start using the vcard standard &
jabber:iq:info.