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...
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...