[Foundation] Growing Concerns for Client Developers

Stephen Lee srlee at sltscommunications.net
Thu Oct 4 11:46:03 CDT 2001

I have to agree with temas on this , one of the other problems that arises
is the implementation of the technology, file Transfer is a prime example,
the way that JIM and winjab implement file transfer is different than the
way that myJabber implements it (yes I realise this is not an xml or even a
jabber issue is just an example). imho it is far easier to  support a
standard at the server end than it is to try and have every client that is
being developed support a set of standards and code practises. there is only
one server (so to speak), but there are many clients.


-----Original Message-----
From: members-admin at jabber.org [mailto:members-admin at jabber.org]On
Behalf Of temas
Sent: October 4, 2001 12:07 PM
To: members at jabber.org
Subject: [Foundation] Growing Concerns for Client Developers

One of the original goals of Jabber was to keep the clients simple, so
that we could have more clients on more platforms.  Some recent trends
in the amount of information and requirements that are being pushed on
to the client are beginning to scare me.  Some of the ideas that are
starting to foster in the JIGs would require clients to implement heavy
protocol pieces and engines such as XPath and XSLT.  While both of these
technologies are great, I feel they are better left to the server side
of things.  Clients should only need to understand simple XML parsing,
namespaces (although that needs to be fixed all over the place), and the
XMLStreams protocol.  We currently have no guidelines or suggestions for
how a JIG should form it's technology, especially with relation to
clients.  Maybe we need an informational JEP outlining the principles of
Jabber XML and client simplicity with regards to protocol handling?  I
think this could greatly benefit newcomers in general and our protocol


P.S. - Yes I am indirectly implying I would work on this =)

More information about the Members mailing list