Hi,

I was just getting around to implementing JCP into the server, and
realized that the server would need to treat a "component" different
from a "user".  The JCP spec also defines a new jabber:component
namespace under which all the stanzas would be sent.

IMO, it would be great for server implementors to have component
connections being accepted on a different port instead of the default
5222.  Also, if a new SRV record could be defined of type
xmpp-component, components can look it up and establish connections to
servers accordingly.

We are already doing it for the jabber:client and jabber:server stream
namespaces... why not for the jabber:component namespace?  This way,
the concerns can be separately and elegantly addressed.

WDYAT?

Regards,
Vinod.

Reply via email to