[JDEV] client "proposal" addendum

[Daniel Arbuckle]

> In reply to your message from the not too distant future: next Saturday AD
> Reply-to: belg4mit at mit.edu
> Return-receipt-to: belg4mit at mit.edu
> Organization: a) Discordia b) none c) what's that?
> Content-Typo: gibberish, charset=ascii-art
> Date: Sun, 12 Sep 1999 01:32:24 EDT
> From: Jerrad Pierce <belg4mit>

I'm not in the future. Are you in the past? ;)

> >(though my inclination would be to write a client that can handle both...)
> >[Daniel]
> Yes well, some believe in the UN*X mantra of do one thing and do it well.

Like me, for example. In this case, the one thing that would be done well
is allowing the users to communicate via the Jabber protocol. If the users
aren't always free to use the client, that hasn't been done well.

> >have a recommended format to store these in, but if we're going to,
> >it should be exceedingly simple. I suggest userid, password, and
> >server one after the other separated with a specific character (say,
> >semicolon) in a specific order (say, userid;server;password), with
> >[Draco]
> Well both the XML and variable=value formats are IMHO simple, and
> intuitive/self-documenting... If you want something compact and 
> unintuitive similar to your suggestion, go with the ftp standard
> user:pass at server
> 
> Of course there's the minor matter ofescaping the delimiting char's in any of
> these formats

XML has a standard way of doing that.

Daniel