Skip to content

added an option to use namespaced instances of socket.io directly #4

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

oneto018
Copy link

With this merge, it would be possible to use single instance of socket.io with multiple chatbots with namespacing option from socket.io.
Basically this allows optional setting (in place of server) socket_io. Thats supposed to be an instance of socket.io or namespaced instance
https://socket.io/docs/rooms-and-namespaces/#custom-namespaces

… customise socket.io config and allow multiplexing single socket.io instance for multiple bots
…ance of namespaced socket.io for customization
@coveralls
Copy link

coveralls commented Oct 11, 2017

Coverage Status

Coverage decreased (-6.06%) to 93.939% when pulling 147db68 on oneto018:master into c3c32d0 on botmasterai:master.

@jdwuarin
Copy link
Member

Hi @oneto018, Thanks for the pull request. Will need to make sure to test that code before I can merge the request.

When doing so, make sure that the tests pass for not only having a scoped namespace per SocketioBot instance, but also within said namespace, using "botmasterUserId" and what happens when the same botmasterUserId is used accross two different namespaces. Really answering the question what should happen in such cases.

@exsesx
Copy link

exsesx commented Mar 26, 2019

Any updates?

@nagarajanSnapwiz
Copy link

nagarajanSnapwiz commented Mar 27, 2019

I am sorry! I completely forgot about this. If this feature is something others interested in, I will write the tests when I have time

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

Successfully merging this pull request may close these issues.

5 participants