Hello. I'm try to use jabberd2 after ejabberd. All work's fine, but
before switching if pyicq-t restarted - my client (pidgin) reconnect to
transport automatic. Now, with jabberd2, i need manually reconnect to
transport. Does this jabberd2 specific?
Thank You.
--
Vasiliy G Tolstov
Dnia 2010-04-26, pon o godzinie 15:42 +0400, Vasiliy G Tolstov pisze:
Now, with jabberd2, i need manually reconnect to
transport. Does this jabberd2 specific?
You need a 'from' or 'both' subscription type for the transport contact
on the roster.
--
To unsubscribe send a mail to
В Пнд, 26/04/2010 в 14:49 +0200, Tomasz Sterna пишет:
Dnia 2010-04-26, pon o godzinie 15:42 +0400, Vasiliy G Tolstov pisze:
Now, with jabberd2, i need manually reconnect to
transport. Does this jabberd2 specific?
You need a 'from' or 'both' subscription type for the transport contact
on
В Пнд, 26/04/2010 в 15:12 +0200, Tomasz Sterna пишет:
Dnia 2010-04-26, pon o godzinie 16:53 +0400, Vasiliy G Tolstov pisze:
where i
can find minimal module development guide for jabberd2? I want to
write some code to support more xep...
Surely.
Dnia 2010-04-26, pon o godzinie 15:42 +0400, Vasiliy G Tolstov pisze:
I'm try to use jabberd2 after ejabberd.
P.S. It's nice to see I'm not the only one in the world, that replaced
ejabberd with jabberd2. It's usually the other way around. ;-)
--
To unsubscribe send a mail to
On Mon, 2010-04-26 at 22:52 +0200, Tomasz Sterna wrote:
Dnia 2010-04-26, pon o godzinie 15:42 +0400, Vasiliy G Tolstov pisze:
I'm try to use jabberd2 after ejabberd.
P.S. It's nice to see I'm not the only one in the world, that replaced
ejabberd with jabberd2. It's usually the other way
