Is there any way to have multiple clients with the same ID connected simultaneously so that requests are sent out in either a round-robin fashion or, better yet, in a somewhat coherent fashion with respect to who is sending the message?
Specifcally, I want to run a back-end service. My service will connect to Jive Messagener just like any other client. People can then send messages to my service’‘s JID. My back-end service receives the messages, processes them, and sends a reply. The problem is, what happens if my server doesn’‘t scale (it’‘s processor intensive)? I’'d like to be able to connect multiple instances of my backend system and have Jive choose one to route it to. Choosing randomly would be ok, but trying to always assign the same user to the same server would make it easy to cache data.
I suspect the answer is no, but I figured I’‘d ask. If I ever get around to implementing it myself (which I may), I’‘d be glad to contribute it back, but since I don’'t know much about Jive, please also consider this a feature req.