jibbr
jibbr copied to clipboard
Evaluate Interface to other APIs
Do we write it so that it can receive and send messages to API's?
Set up a generic interface for all APIs to message?
As I see it we have two branches at the moment
- Those things that should work like regular sprockets...aka command-reponse
- Those that should periodically push x messages to the room, like the pull from twitter
Could it be an idea to have a given set of (news)tickers be somewhere...I'm not sure I like the idea of having the scheduler pushed inside the stomach of Jabbot, but could do some encapsulation that have the knowledge of Jabbot and the Scheduler so it could orchestrate the messages from the scheduler to Jabbot
Random stuff from the top of the head here :)
Propose as post-Code52 work