On 9 Feb 2007, at 11:08, Quentin Mathé wrote:
Do you mean with 'transport' facility? On libgaim website, I read the following excerpt:
Yes, that's right.
However it isn't clear to me whether 'transport' implementation code must be on server or client side? Perhaps it can be implemented either way?
Jabber transports are server-side. They are gateways between different protocols; I connect to my Jabber server, and it makes people on other networks appear to be Jabber users, so the MSN user [EMAIL PROTECTED] would appear to be the person% [EMAIL PROTECTED]
Also do you know jabber servers that support main proprietary protocols MSN, Yahoo, AIM through this transport mechanism?
There is a standardish mechanism for supporting transports, based on the old Jabberd 1.x series internal protocol. All of the major servers (Jabberd 1/2, eJabberd, etc) support them. The transports run as external processes (typically written in Python using the Twisted framework) and connect to the Jabber server via a socket. I run an AIM (and ICQ, since they are now the same network) transport and an MSN transport on my server. There are also transports available for Yahoo, gadu-gadu etc, but since I don't know anyone who uses these, I tend not to bother with them.
_______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
