-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Create a websocket server enabled Botkit connector which can manage multiple remote clients #871
Comments
The code for this is available in this pull request: I've also created a simple web client starter kit, which will pull the Botkit dev/webchannel branch by default until this is merged into master: |
can we use this library https://github.com/primus/primus to let the user use any socket library he wishes to. |
@MunawwarHussain That is very interesting! I'll have to take a look. What are the alternative socket libraries you are interested in? |
@benbrown we are waiting for something like this!!! Is it possible to use the Web Bot without a Botkit Studio token, running in my own server? |
@maxmeinberg Yes! You can run it standalone like any other integration, but studio will greatly extend it's capabilities. |
@benbrown no problem as such its good to have an abstraction and make it library independent. |
@benbrown I'm trying to use this Web Bot with my existing Facebook bot and got this error message Is it possible to use the Web Bot in same server with Facebook Bot and Watson? This is part of my code: // Customize your Watson Middleware object's before and after callbacks. middleware.after = function(message, conversationResponse, callback) { Thank you very much!! |
@maxmeinberg That should work, as you pass in middleware depending on Node's ENV variable setting! Would be interesting how you handle of different tokens depending on the Bot's realm (that is Facebook, Slack and the like). |
+1 |
This represents an important next step on the roadmap for Botkit: a native communication channel that allows Botkit to talk directly to the web, native clients, or custom platforms.
This is ACTIVELY UNDER DEV and slated for release for a few weeks from now!
Amongst the many todos:
The text was updated successfully, but these errors were encountered: