[JDEV] Standards

[Andrew Salamon]

> Quoting Peter Millard <peter at vantek-corp.com>:
> > 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.
> 
>   And if that information is pretty much useless for other clients, why burden 
> client developers with a 'universal config format'?  Example would be under 
> Windows.  Windows uses the registry for virtually everything, and many, MANY 
> developers will end up using it.  Under Linux, it's a different story.  And 
> then there's the Mac.. ;-P

  I can't speak for anyone else on the Mac team but I always figured 
MacJabber would use an xml format for preference (config) info.  
Whether that is stored on a server (with only host, port, login name 
held locally) or all stored locally doesn't seem to make much 
difference to me from a programming point of view. I haven't looked 
at the jabber:iq:info namespace so I don't know how it would work, 
but I'd be glad to support whatever crossplatform stuff was decided on.

Andrew
salamon at home.com
http://members.home.net/salamon