Before a full features whack why do you don’'t provide a XMPPComponentConnection (extends XMPPConnection) in SMACK (or SMACKX) before. It just needs a custom PacketReader, a custom PacketWriter and the probe type allowed in Presence. Everything else that a component must do should become a listener work (probe replies, etc…) . I made this for a project, are you interested in this contribution?
I can provide you the code but my intention is to have that in SMACK, that way all people that want to use it doesn’'t need a new custom build of SMACK each time a new version comes out.
or … how about a community driven fork of smack which synchronizes regularly with the official jive smack version … keeps the license compatible… integrates as much custom patches as possible and also produces nightly builds ?..
I’‘d be very happy with this, and if it works as advertised it would make writing a basic external component trivial. So how’‘s it going? Any inkling of whether it’'ll be integrated, yet?
There do seem to be problems with startup reliability (occasional SSL and socket exceptions can happen upon connect), and Wildfire doesn’'t pick up the name/category/type and such as it should.
It seems that there are some alterations made to Smack to allow this to function. Something like a constructor made public or some such? Standard Smack libraries don’'t work.
I’'d like the source to be published, even if it were not Smack-incorporated. The sheer simplicity of making a simple bot or transport-framework using this method is too good to pass up.