I see no problem, write separated jabberd module and also apache module for java support. Apache moduleAnother, IMO larger, problem is that not everyone is able/allowed to install/configure Apache modules. IMO it whould be best to just create some kind of very simple C, Perl or whatever daemon that can be run on the webserver. But even that will give a lot of problems to quite a lot of people that don't have sysadmin rights on their server.
only would forward data to jabberd module.
Apache is not very stable, and most important think in webclient is not
losing messages.
Who is being targeted anyway? Only large organisations that can modify their http server, almost everyone with a PHP homepage or something in between?
--
Bart van Bragt
"Take my advice, I don't use it anyway."
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
