On a related note - what is the best (cleanest, portable) architectural component/module to use when planning to build an 'module' that terminates traffic for a subset of 'users' in a domain - almost like a connection manager but the routine client capability is self-contained inside the module for each end user represented by the 'module'
Trying to build a high performance specialized application where human users are paired with their individual 'message sink' for various application specific reasons - communication is via XMPP and the message sink appears to be just another xmpp user with presence and messaging capability. Have considered the external bot route (too many replicated bots to run) and would like not to have to add special code to the core xmpp router to do this via some sort of a filtering plugin. The connection manager approach would be almost correct but there seems not to be a standard for that across xmpp server implementations ? ) Peter Saint-Andre <[EMAIL PROTECTED]> wrote: Resource binding applies to clients, not components. Peter
