Hi there,
I’'m using a modified Smack library to build an external component, a transport. The library was first mentioned here:
It connects, subscribes, sends stuff back and forth, but I’‘ve found some quirky issues which may be related to Wildfire. After a while (undefined period), the component doesn’‘t receive things like messages or presence stanzas from the server. Any messages and presence stanza’‘s sent from the legacy network arrive fine, and Wildfire says the component session still exists (otherwise legacy2xmpp couldn’‘t work). I have not been able to find a cause for this in the modified Smack (though it’‘s closed source, still), I have determined that it’'s “processPacket” method is not called. Any ideas?
Another problem I’'m having is related to broadcasting of presence information. To send presence info of a given legacy user (who has been subscribed to), I have tried:
-
Sending without a ‘‘to’’ (doesn’'t arrive anywhere);
-
Sending to a bare jid (arrives at the highest priority logged in session, should arrive everywhere);
-
Sending to all full JIDs I know (all stanzas arrive at the highest priority session).
The latter two cases seem like incorrect handling of presence stanzas if I’‘ve read the RFC’'s right. Any help on how to do this?