Consider supporting dynamic namespaces

[davidbau]

Consider supporting dynamic namespaces. Dynamic namespaces are a key tool for environments where all the complex application logic is in the browser, and the server just wants to reflect. They allow modularity without special server help.

I've implemented dynamic namespaces here as a subclass of socket.io Server:
https://github.com/PencilCode/dynamic.io

That page explains the idea. Basically, it adds a new server.setupNamespace(pattern, callback) to handle "new namespace" callbacks (return false to reject the namespace). Dynamically created namespaces expire after all sockets disconnect.

This is also helpful for setting up subdomains. Constructing a server with { host: 'myhost.com' } adds qualification of namespaces are by-host. nsp.fullname() returns strings like "//myhost.com/mynsp" (except for config.host, which retains the default "/", to stay compatible with the base class). This dovetails well with dynamic namespaces for sites that use DNS subdomains for organizing projects.

Consider including this functionality in the socket.io Server base class itself so that this subclass is unnecessary.

[davidbau]

This project has been updated with tests now. The subclass passes all the socket.io unit tests (i.e., it behaves perfectly as the base class when you don't do anything new) as and it adds its own tests.

[dylanlingelbach]

The dynamic namespace functionality would be useful to me as well.

[alberto-f]

Is there any news on this topic?

[dylanlingelbach]

@alberto-f - I have an open PR here however I haven't received any feedback in a while. Hope that helps!

[darrachequesne]

That issue was closed automatically. Please check if your issue is fixed with the latest release, and reopen if needed (with a fiddle reproducing the issue if possible).