Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Async Namespace Initialization #1

Open
msamblanet opened this issue Jan 30, 2015 · 0 comments
Open

Async Namespace Initialization #1

msamblanet opened this issue Jan 30, 2015 · 0 comments

Comments

@msamblanet
Copy link

I would like to test the dynamic namespace names against some of my DB data to assert if they should be created or not. This would require the setup callback to have a next() or some similar pattern as opposed to synchronously returning true or false.

Is this even possible the way the connect.io is written? I have only briefly looked and it did not look promising...

If not, is there a way to destroy a namespace that was created? That way I at least limit how long the rogue channel is open...would be even nicer if it could be "paused" to prevent any activity...

DynamicNamespace.remove at first glance does not seem correct since I want to disconnect the sockets and not wait for the timeout in this case...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant