JD Conley wrote:
In the multi-service enabled endpoint you'd just have to have a lookup table mapping a given JID to its current type (chat room, pubsub service, etc). We already do this today in our server for managed group aliases and such. The service can no longer be a completely separate entity. The endpoint simply must know about all the services and all the JID's under the domain in order to properly handle messages.
Sure, you could implement your server that way. The original jabberd server used subdomains so that has become customary, but I don't see any reason why it would be necessary.
Peter
smime.p7s
Description: S/MIME Cryptographic Signature
