[Standards-JIG] Component protocol : JEP 114

Peter Saint-Andre stpeter at jabber.org
Wed May 10 22:41:02 UTC 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mridul Muralidharan wrote:
> Hi,
> 
>  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. I realize this is kind of
backwards from the XMPP perspective, but in large measure JEP-0114
documents existing practices from a long time ago.

You can think of it this way: the component doesn't have a JID, it's
just some entity out there. It "wants" to be plays.shakespeare.lit or
whatever, so when it connects to the server it puts that component JID
in the 'to' address.

> Finding out the (default) domain of the server is something which would
> be necessary for the component client.

Are you talking about virtual domains? So let's say the server hosts
both shakespeare.lit and hamlet.lit. Your question is: "how does the
component know which domains the server hosts, and therefore how does it
know what component JID to request?" Correct?

Peter

- --
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEYmv+NF1RSzyt3NURAiPPAJsExzC8KFmO2d0mUE1hJBSZKFP+EACgsjrs
zziVxMYghPp/JaGeVAo4g2o=
=dwx7
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20060510/738b6963/attachment.bin>


More information about the Standards mailing list