You should expect the same behavior for different accounts. However, exceptions are thrown if the account doesn’'t exist, if the password is invalid, or the server is not reachable.
A good way to start, is to test using Exodus against Messenger (Exodus has an option to let you see the XML it’‘s sending/receiving - very handy to see what’‘s going on under the coversr). That will get your addresses, passwords, etc all figured out. Then substitute an instance of your Smack client (with the smack debug flag passed in) to see what smack is doing - and what it’'s doing differently).
Once everything is working with Messenger, Exodus, and one custom Smack client, you can pull Exodus out of the mix and do direct conversations between Smack clients through Messenger.
It seems like more work but it actually goes much faster this way. Messenger and Exodus are ‘‘known good’’ working together which eliminates everything except your setup. Then you can start experimenting with Smack knowing that it is the only variable in the mix.
In this project the machine(machine name) is the user
and may or may not be known in advance. Are there any
plans to allow client registration but an admin will
need to accept the registration before the “user” can
use the system?
Yes. In messenger, log into the web admin, and turn auto-registration off. That prevents in-band automatic registration. Then it’'s up to the adminstrator to create new user accounts using the web admin interface.
New users can request new accounts using some other mechanism (maybe a web page or email). If you’'re looking for anonymous logins, they are also allowed in Messenger (and that can be enabled/disabled through the web admin interface). That way you can login without an account (handy for open chats, etc).