[Foundation] Growing Concerns for Client Developers

Peter Saint-Andre stpeter at jabber.org
Thu Oct 4 12:33:18 CDT 2001


Thanks for bringing this up. I don't think anyone wants Jabber clients to
become as bloated as browsers. On the other hand we're trying to build in
more advanced functionality such as file transfers, browsing, forms,
conferencing, whiteboarding, and so on. I'm a firm believer in keeping
things simple, however there are uses for Jabber way beyond IM and perhaps
it's best to differentiate between core messaging functionality and the
more advanced stuff. At some point it will be hard to know just by looking
at an application whether it really is a Jabber "client" (it could be as
small as a news ticker with no chat capabilities or as large as an
integrated development or content management application a la Groove).

I feel that in order to perform simple functions, simple XML (the current
protocol) should be all that is required. The question is how simple do we
want to keep the protocol in order to complete more advanced use cases?

Peter


On 4 Oct 2001, temas wrote:

> 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
> designers.
> 
> --temas
> 
> P.S. - Yes I am indirectly implying I would work on this =)
> 




More information about the Members mailing list