Hi! On Mon, Aug 10, 2009 at 22:15, Niklas Gustavsson<[email protected]> wrote: > On Mon, Aug 10, 2009 at 9:54 AM, Michael Jakl<[email protected]> wrote: > So, in addition to the component support (using the component > protocol), how about we allow for registering modules with a > subdomain? For example, adding a XMPPServer.addModule(String > subdomain, Module module) method. Then we do a > SubdomainHandlerDictionary working similar to the > NamespaceHandlerDictionary which takes care of finding the handler. > > That way, we can have the server respond to different subdomains in an > easy way. What do you think?
That's exactly how I'd do it. If it's no problem that subdomain routing takes precedence over namespace routing this is the way to go IMHO. On a second thought we might want to keep the namespace routing within the subdomain routing. Is there a use-case where we need to route by subdomain first, then by namespace or should the module take care of that? In the pubsub case, we have two namespaces (the "general" namespace and the "owner" namespace). In my case it's handled by the same module, but is this always the case? Michael
