[JDEV] Jabber as Application Middleware

[Kit McCormick]

On Tue, 6 Mar 2001 eric at openthought.net wrote:

> Well, count me in.  I definatly think it's possible to do all this without
> modifying Jabber at all.  However, Dave mentions (on his website, see the
> previous message in this thread) a few ideas that Jabber might be able to
> implement that could make Jabber a more robust middleware application.  His
> ideas include message queueing, message timeouts/retry, and so on.  I definatly
> feel these would be appropriate, but maybe somebody more knowledgable then
> myself could take a look at his page and discuss why to or why not to implement
> such ideas.

I've been trying to figure out if namespaces + server extensions would be
a good place to start.  But I can't figure out the implementation details.
Do message namespaces map to server extensions?  If so, is this 
implemented yet?  My first use of jabber as middleware will be to plug
non-java clients in to an existing JMS (java message service)framework.

To me, RPC over a message service is awkward.  I would rather see a
sender/listener paradigm, where the sender exposes itself as a listener
(eg: ReplyTo) if it wants a response.

Kit