Le 9 févr. 07 à 11:09, David Chisnall a écrit :
On 9 Feb 2007, at 06:21, Yen-Ju Chen wrote:
Besides a native XMPP support,
libgaim is interesting to consider for other protocols:
http://gaim.sourceforge.net/sean/blog/a_new_blog
Aside from the fact libgaim is an incredibly buggy, badly written
abomination, I don't really see the need to support other
protocols. XMPP is an open standard, and now that it's backed by
Google it's starting to gain traction. If you need support for
proprietary legacy protocols, this is better handled on the server
side, where it's easier to upgrade when the authors of the
protocols decide to change things.
Do you mean with 'transport' facility? On libgaim website, I read the
following excerpt:
"Jabber also has what they call a "transport". A transport is a way
of connecting to another IM service, such as AIM or ICQ. In order to
use a transport, you "subscribe" to it, which is sort of like adding
it to your buddy list, except you must also provide a valid username
and password (e.g. if you were subscribing to the AIM transport, you
would tell it your AIM username and the password for that account).
Once you have subscribed to a transport, it will sign onto that
service using the specified username, and you can talk to people
using that service - their username would be
[EMAIL PROTECTED], for example. The username they would see
is the one you subscribed to the transport with. Currently in Gaim,
you cannot subscribe to a transport - however, if you subscribe to a
transport using a different client, Gaim can make use of it."
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?
Also do you know jabber servers that support main proprietary
protocols MSN, Yahoo, AIM through this transport mechanism?
Cheers,
Quentin.
--
Quentin Mathé
[EMAIL PROTECTED]
_______________________________________________
Etoile-dev mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-dev
