The preferred way forward with transports is to migrate to external
transports, generally this also means the python based ones instead of
the old c based ones.
i.e. {jabber-aim, jabber-icq, jabber-msn, jabber-yahoo} are deprecated
in favor of {pyaimt, pyicqt, pymsnt, pyyimt}
--
- Norman Rasmuss
Hi,
There's also JCR: http://jabber.terrapin.com/JCR/
It's documented in the jabberd2 docs:
http://jabberd.jabberstudio.org/2/docs/section05.html#5_9
I'm not sure whether that's even worth packaging. On one hand, having
legacy services is certainly desirable (and jabber1 leaks memory for
me)..
On Nov 6, 2005, at 2:00 AM, Roland Stigge wrote:
Does this mean that in order to run a 2.x server working with the above
transports, you also need to run the jabber 1.x server, i.e. both
servers (running on different jabber domains / hosts?)?
Yes, for the packaged transports you have to have t
Hi Jamin,
Jamin W. Collins wrote:
>> ===
>> ===
>> [...]
>> With additional transports and/or services, Jabber supports connecting
>> to AIM, ICQ, IRC, MSN and a lot of other chat networks. These transports
>> and service
On Nov 4, 2005, at 2:44 PM, Roland Stigge wrote:
Package: jabberd2
Version: 2.0s10-1
Severity: normal
Hi,
the package descriptions read:
===
===
[...]
With additional transports and/or services, Jabber supports con
Package: jabberd2
Version: 2.0s10-1
Severity: normal
Hi,
the package descriptions read:
==
[...]
With additional transports and/or services, Jabber supports connecting
to AIM, ICQ, IRC, MSN and a lot of other chat ne
6 matches
Mail list logo
