Although the pile of code works, it’'s pretty
ugly. It does, however, include some registration
and roster code.
If you have some good snippets, that would be cool. Otherwise, your general logic might be useful to apply to Smack.
My project is nearing release and I am considering
re-implementing the core with Smack. Should I do
this, I would love to contribute back to Smack.
That would great and your feedback/contributions would be appreciated.
Where do you see Smack going?
We hope it will continue to evolve to become a truly useful tool for those talking to Jabber servers in Java. Other interesting integration possibilities exist as well, such as having message driven beans (EJB), but driven by Jabber events instead of JMS.
Why was it originally created?
Part of the reason we created it was that we had the need for a good general purpose library and weren’‘t happy with the current solutions. Open Source is the perfect way to develop that kind of technology. Further, we’'ll soon be announcing a commercial Java Jabber server, so Smack is also a tool for those customers and to attract new customers to the server.
IMHO, a good Java API is what Jabber needs
to really start cooking.
Yep, I agree! BTW, I hope to have Beta 2 available at the end of the week or early next week. None of the roster code has been started yet, so there is much work to be done.