-
Notifications
You must be signed in to change notification settings - Fork 27
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
Port Jabbot from Console app to ASP.NET MVC #12
Comments
Doing it in SignalR - so we have a bot in SignalR talking live back to the chat room was a great suggestion. SignalR <--> SignalR - keeping both live. |
***************** WE'RE LEAVING IT IN CONSOLE TO BEGIN WITH - WILL ADVISE WHEN WE'RE RIGHT TO CHANGE OVER |
This has been started, but with NancyFx rather than ASP.NET MVC |
Any reason for the switch from MVC to NancyFx? |
Nancy's really nice. Also thats what @shiftkey had made it before he told me to go nuts. |
To clarify, we went with NancyFx because @sethwebster contributed the initial web code. |
We need to get Paul Stovell to submit some initial code, so that we're all On 12 January 2012 22:31, Brendan Forster <
|
I've got a working Nancy host working on AppHarbor -- it's running twitterbot. I went with Nancy for fun, more than as a design decision. I've gotten around the App recycling using my MomentApp nuget package. Basically, upon app start, the app creates a scheduled moment job to ping the service again in 2 minutes, once that happens, another scheduled job is created and so forth. Something more robust would be needed for a mission critical app, but this strategy is simple, and free. |
Gotta agree with @sethwebster on this - plus we've had the NancyFx guys hanging out in the chatroom to help with a couple of questions. |
http://nuget.org/packages/SignalR
https://github.com/davidfowl/Jabbot/
Starts a app-pool-recycle resillient worker process for checking messages sent to it, and returning messages.
Can we do a persistent connection from an ASP.NET page, or would we have to do a hosted bot somehow?
The text was updated successfully, but these errors were encountered: