[jdev] Re: JEP-114 - what is the "component name"?

[Gaston Dombiak]

Hey ralphm,

My question was/is about the format of the TO attribute when sending the 
opening stream:stream element. So is it valid to just include the subdomain 
instead of the subdomain+hostname? There is no description of that in the 
JEP, just the examples that are using the format subdomain+hostname.

Your post made me have more questions now. :) So is it valid to send 
subdomain+anyhostname to a server whose hostname is not anyhostname?  Where 
can I read about the implications of doing something like that? How may a 
server differentiate between subdomain and subdomain+anyhostname? Do they 
have different implications?

Thanks for your help.

Regards,

  -- Gato

"Ralph Meijer" <jabber.org at ralphm.ik.nu> wrote in message 
news:20050721185823.GA73894 at ik.nu...
> On Thu, Jul 21, 2005 at 03:23:30PM -0300, Gaston Dombiak wrote:
>> I've been reading again the JEP-114 (Jabber Component Protocol) since I
>> wanted to check the formal definition of what is called the "component
>> name". In the JEP I see that the example is using 
>> 'plays.shakespeare.lit'.
>> Since in general the spec is using 'shakespeare.lit' as the hostname of 
>> the
>> server I assumed that the "component name" is formed by the component
>> subdomain + the server hostname. So my question is: should "component 
>> name"
>> be of the form <subdomain>.<server-hostname>? Is it correct to just use
>> <subdomain>?
>
> You may use any hostname, it doesn't have to be local. In fact, if you
> don't need the component to be reachable from other servers, but only
> available for the users of your server, you can assign it
> 'component.localhost' or 'component'. A server will usually first check
> known hostnames, before trying DNS lookup.
>
> -- 
> Groetjes,
>
> ralphm