[JDEV] Customizing Jabber server

[Gerard BUNEL]

wasted a écrit :

> we're working on similar types of issues and my take on it this... jabber
> isn't an "application server" itself.  it facilitates the routing of
> messages to the appropriate destination - normally a human for chat.  of
> course the destination can be an "agent" or a transport with
> business/application logic coded for a purpose which returns some data or
> whatever.  an "agent" could be a stock watcher, a "weather man", a news
> grabber, data mine - the list is endless.  you can write an "agent" in
> almost any language with all the cool tools the dev guys have done -
> Net::Jabber, JabberCOM, JabberBeans, etc...  i'm partial to JabberBeans
> 'cause we do a lot of Java programming.  then again, as "JAM" develops,
> jabber could become more "application server"-ish.
>
> not sure if that's the sorta explanation you're looking for, but i hope it
> helps.

I'm not trying to "application-server"-ish the jabber server.
I just want to filter some parts of the jabber protocol so that information is provided by the application server
instead of the Jabber server itself (by the mean of the default xdb_file).
I think that for authentication, Rosters, vCard this can be obtained by bootstraping the xdb_file
to delegate the requests to the application server (that we also develop, this is a specialized one, not a J2EE server).

Our application server is Java based and we also have a look to JabberBeans.
I've also pointed out the JAM effort on Jabber but, as I need such functionalities rather quickly
(Pre-version for July) we focused our interest on Xml-Rpc and made some trials in embedding Xml-Rpc
requests into the Jabber protocol. We did that successfully.