Hi.
I view the source of jivemessenger, but i don’‘t find the way that user’‘s server deliver message to other components. and after session is setuped, server start to accept and read some message,persence or iq. when server accept a message, and the message need to be sent other server ,or contact’'s server, but where do this action(send) finish?
best regards
I view the source of jivemessenger, but i don’'t find
the way that user’'s server deliver message to other
components.
When a new component is registered a route to the component is created. See: InternalComponentManager#addComponent(String, Component) and RoutingTableImpl. The server uses routes for locating session (user sessions, external component sessions and components).
and after session is setuped, server
start to accept and read some message,persence or iq.
when server accept a message, and the message need to
be sent other server ,or contact’'s server, but where
do this action(send) finish?
We do not currently have support for server-2-server communication. Though it is in our immediate roadmap.
Regards,
– Gato
Hi Gato！
By the way, which version do you want to support JEP-0114 ,and s2s communication ?
Best Regards
I’'m not sure what you are asking. For external components we decided to follow JEP-114 (which has already been implemented) and maybe in a future release include some extensions proposed in the jabberd2 component JEP. Regarding s2s we will implement the specification defined at http://www.xmpp.org/specs/rfc3920.html and http://www.xmpp.org/specs/rfc3921.html.
Let me know if you were asking something else?
Regards,
– Gato