Using SMACK for communications through gateways (ICQ/AIM/etc)

jdevelop wrote:

  1. request registration packet
  1. send registration information with given key, username/password etc

1-2 has only to be done once, it’'s permanently stored on the server.

  1. check registration status

Don’'t know what you mean by that.

  1. send presense packet?

That’'s not explicitly required when the transport is on the roster.

  1. send/receive various event

This doesn’'t need any special treatment compared to normal XMPP communication.

  1. deregister

Only required when you never want to use the transport again (with that identification).