adrian at kilipir.ro
Fri Jan 10 08:31:38 CST 2003
> Matthias Wimmer wrote:
>> Hi Lukas!
>> lukasm wrote:
>>> Apache module is not good idea. I would write normal jabberd module
>>> with listen socket.
>>> Then PHP or java or .... can connect to that module and take data.
>>> Not everybody use apache and PHP.
>> The problem if you don't write it as a module for your webserver is,
>> that you can't use it from Java applets as they only can connect to
>> where they have been loaded from (same is true for other things like
>> If you write it as an extension to the Jabber server you either have
>> to listen on an other port or ip address then the webserver. If you
>> use an other IP address you have the descibed problems, if you use an
>> other port you can get in problems with restrictive web proxies ...
>> and they are one of the reasons why web clients are used most.
> I see no problem, write separated jabberd module and also apache module
> for java support. Apache module
> only would forward data to jabberd module.
> Apache is not very stable, and most important think in webclient is not
> losing messages.
Another good point. I have to think ant take a decision, also if you saiy
that apache is not very stable... then remains the other option an
indepedent client that is launch on the server when i load the page, and
kill him on dissconenct or after an timeout. a perl client might be good
>> Tot kijk
> jdev mailing list
> jdev at jabber.org
More information about the JDev