Skip to content
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

Evaluate Interface to other APIs #3

Open
andrewtobin opened this issue Jan 9, 2012 · 2 comments
Open

Evaluate Interface to other APIs #3

andrewtobin opened this issue Jan 9, 2012 · 2 comments

Comments

@andrewtobin
Copy link
Member

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?

@cyberzed
Copy link
Contributor

cyberzed commented Jan 9, 2012

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 :)

@shiftkey
Copy link
Member

Propose as post-Code52 work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants