[JDEV] Standards

[Dave Smith]

One file is all that's required w/ hostname,port, proxy, port, username &
password (optional). The rest can be retrieved and stored as necessary from
the jabber server. I imagine it would make sense to take this one step
further and create a seperate namespace for configuration related data so
that we could structure it accordingly (versus uploading in <x> tags). I
discussed the issue briefly w/ Jer on #jabber and he said that this kind of
functionality will be put in eventually, but we need to iron out the
specifics.

Insofar as storing the stuff on disk..well, if the client so wishes, *but*
there's no reason to say the client *must*. In theory, a author could
request the data at the beginning of the session and upload/push new changes
whenever a change is made. That would provide better fault tolerance and
remove the need for seperate files.

D.
----- Original Message -----
From: "Jerrad Pierce" <belg4mit at CALLOWAY.MIT.EDU>
To: <jdev at jabber.org>
Sent: Wednesday, January 26, 2000 1:37 PM
Subject: Re: [JDEV] Standards


> .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)
>
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>