[Standards-JIG] Component protocol : JEP 114
mridul at sun.com
Thu May 11 04:57:38 UTC 2006
Peter Saint-Andre wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Peter Saint-Andre wrote:
>>Mridul Muralidharan wrote:
>>>> It would be great if someone could clarify this for us.
>>>>In section 3 (Protocol flow) of the JEP , it is specified that the 'to'
>>>>while opening the stream should be the component jid , but nothing is
>>>>mentioned about the 'from' for the response from the server.
>>>>The example gives the impression that the 'from' should be the component
>>>>jid itself , while xmpp specifies that it should be the server domain.
>>>>Which of this is correct ?
>>In the stream header from the server to the component, the 'from'
>>attribute is set to the component JID.
>BTW, that is for the jabber:component:accept namespace, since the server
>accepts connections from the component when that namespace is used.
>By contrast, the server initiates a connection to the component when the
>jabber:component:connect namespace is used. This is less common.
>(Older methods also included jabber:component:exec but that is not
>documented in JEP-0114 because connecting via STDIO is discouraged.)
I was not aware of the exec namespace , interesting - will try to find
some doc about it.
We support the accept namespace as of now - I was aware of the connect
namespace but dont recall much about it.
Is the intention that there is a component bound to a port waiting for
connections and the server actively connects to it in response to some
client request sort of thing ?
Something along the lines of s2s ?
Thanks for clarifying.
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.1 (Darwin)
>Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>-----END PGP SIGNATURE-----
More information about the Standards