External components seem to be the better choice if you can use them. This
leaves the core server to do what it was made for, routing xml, all
processing is pushed out to separate apps. There is a limitation to the
external component model right now, that is all messages destined for an
external component must be addressed to that component. This means that it
is hard, impossible to write a component that will log all traffic through
the jabber server.
For that job you need to use a jsm module, which is build into jsm.so.
Depending on where you place your load configuration, you can receive every
packet going through the server.
There are steps being taken to change this, as of 1.4.2 you can copy (bcc)
any jid on all presence changes, so maybe all packets or all messages or
something is not far behind.
Just my observations, please correct me if I am wrong.
Glenn
----- Original Message -----
From: "Frederic FELTEN" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, March 13, 2002 6:01 AM
Subject: [JDEV] module development
What is the good way to develop a jabber module ? External
(with JECL for example) or internal with the 'load' method ?
And why ?
thanks
_________________________________________________________
Le journal des abonn�s Caramail - http://www.carazine.com
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
