ruote as a webhooks engine
13 views
Skip to first unread message
orlin
Jun 19, 2009, 12:32:36 PM6/19/09
to Web Hooks
I wonder if ruote can be used as webhooks engine (ruote-rest in
particular).
http://openwferu.rubyforge.org/
The idea is to dynamically create trivial infinite-loop processes. Of-
course it was made to do much more. Which is great. It already
supports a variety of listeners to trigger the hooks with: SQS, XMPP,
Atom feeds, etc. And REST is just one kind of a callback
"participant".
It's almost too good! What do you think? Anything missing?
Orlin
particular).
http://openwferu.rubyforge.org/
The idea is to dynamically create trivial infinite-loop processes. Of-
course it was made to do much more. Which is great. It already
supports a variety of listeners to trigger the hooks with: SQS, XMPP,
Atom feeds, etc. And REST is just one kind of a callback
"participant".
It's almost too good! What do you think? Anything missing?
Orlin
Jeff Lindsay
Jun 19, 2009, 4:33:37 PM6/19/09
to webh...@googlegroups.com
I like it. I've been watching it for a while. Workflow stuff with
webhooks is really interesting to me. I've been thinking about it
forever, but not actively doing in hard thinking with it. You could
use webhooks with any workflow engine though. You can also do workflow
without an engine.
But yes, this is cool. However, I haven't seen the listeners your
talking about. Are they in a different package? Maybe they're hidden
as participants. They don't seem to separate them out into separate
files. And quickly looking at their docs, I didn't seem to get this
info.
-jeff
--
Jeff Lindsay
http://webhooks.org -- Make the web more programmable
http://shdh.org -- A party for hackers and thinkers
http://tigdb.com -- Discover indie games
http://progrium.com -- More interesting things
webhooks is really interesting to me. I've been thinking about it
forever, but not actively doing in hard thinking with it. You could
use webhooks with any workflow engine though. You can also do workflow
without an engine.
But yes, this is cool. However, I haven't seen the listeners your
talking about. Are they in a different package? Maybe they're hidden
as participants. They don't seem to separate them out into separate
files. And quickly looking at their docs, I didn't seem to get this
info.
-jeff
Jeff Lindsay
http://webhooks.org -- Make the web more programmable
http://shdh.org -- A party for hackers and thinkers
http://tigdb.com -- Discover indie games
http://progrium.com -- More interesting things
orlin
Jun 19, 2009, 6:16:15 PM6/19/09
to Web Hooks
Gotta say, I'm a big fan of your hooks, man! Had some vague ideas in
the past, kind of similar, but not quite worked out, it just helps so
much to follow such clearly articulated activism. In contrast, I've
had ruote in mind for other things, but it took a while to connect the
dots... It was so obvious (staring me in the face), then it hit me on
idle gear, I thought I was imagining things earlier today :)
This is the first "workflow engine" I can stomach. I like Ruby and
friends. Python (as a service) I guess, but not quite the same. I've
had my sorry attempts to reinvent the wheel (php + mysql). It wasn't
fun. So it's always good when there is solid opensource that is fun
to work with.
Now, I haven't really looked at ruote yet, but it seems to me that
listeners is what comes in as event triggers. Participants is what
goes out (the callback) to activerecord, activeresource, xmpp, etc.
According to a slideshow http://www.slideshare.net/kenneth.kalmer/ruote-in-20-minutes
- mostly.
I wrote to John about it. This is the kind of cause than can give
ruote more visibility too. Hopefully he'll join the conversation with
good news. In my application l'll need more or less instantaneous
response (functionality extensions / plugins). Some types of
notifications can get away with taking their time. In this case, I
need something that will fire the callback immediately and get results
back (as if it's the same app).
Cheers,
Orlin
> Jeff Lindsayhttp://webhooks.org-- Make the web more programmablehttp://shdh.org-- A party for hackers and thinkershttp://tigdb.com-- Discover indie gameshttp://progrium.com-- More interesting things
the past, kind of similar, but not quite worked out, it just helps so
much to follow such clearly articulated activism. In contrast, I've
had ruote in mind for other things, but it took a while to connect the
dots... It was so obvious (staring me in the face), then it hit me on
idle gear, I thought I was imagining things earlier today :)
This is the first "workflow engine" I can stomach. I like Ruby and
friends. Python (as a service) I guess, but not quite the same. I've
had my sorry attempts to reinvent the wheel (php + mysql). It wasn't
fun. So it's always good when there is solid opensource that is fun
to work with.
Now, I haven't really looked at ruote yet, but it seems to me that
listeners is what comes in as event triggers. Participants is what
goes out (the callback) to activerecord, activeresource, xmpp, etc.
According to a slideshow http://www.slideshare.net/kenneth.kalmer/ruote-in-20-minutes
- mostly.
I wrote to John about it. This is the kind of cause than can give
ruote more visibility too. Hopefully he'll join the conversation with
good news. In my application l'll need more or less instantaneous
response (functionality extensions / plugins). Some types of
notifications can get away with taking their time. In this case, I
need something that will fire the callback immediately and get results
back (as if it's the same app).
Cheers,
Orlin
orlin
Jun 22, 2009, 6:45:59 AM6/22/09
to Web Hooks
John says: "very nice idea" ...
This depends on the load of the engine and its configuration, but it's
not immediately. The engine has to retrieve the target expression,
reply to it with the incoming workitem and thus the process resumes.
At one time, 1 expression operation apply/reply is in effect.
So it's not immediate but I guess your listener could reply
immediately with something like "wait, answer is coming" and then the
next step in the process could post back to your client application
(maybe with the information provided byt he listener / webhook via the
workitem). That's the general use case for participants / listeners.
Now if you really want the hook/listener to provide an answer (hiding
the asynchronocity of ruote), you'd have to poll ruote about it, shoud
be under 350ms.
A better/faster ruote is in preparation : http://github.com/jmettraux/ruote/tree/ruote2.0
This depends on the load of the engine and its configuration, but it's
not immediately. The engine has to retrieve the target expression,
reply to it with the incoming workitem and thus the process resumes.
At one time, 1 expression operation apply/reply is in effect.
So it's not immediate but I guess your listener could reply
immediately with something like "wait, answer is coming" and then the
next step in the process could post back to your client application
(maybe with the information provided byt he listener / webhook via the
workitem). That's the general use case for participants / listeners.
Now if you really want the hook/listener to provide an answer (hiding
the asynchronocity of ruote), you'd have to poll ruote about it, shoud
be under 350ms.
A better/faster ruote is in preparation : http://github.com/jmettraux/ruote/tree/ruote2.0
John Mettraux
Jun 22, 2009, 11:19:36 AM6/22/09
to Web Hooks
Hi Orlin and Jeff,
yes, discussing it at :
http://groups.google.com/group/openwferu-users/browse_frm/thread/2e8d8a82b87ec11f
Glad to team with Orlin on that.
I've just joined this list, hello everyone, nice to meet you.
Cheers,
John -- http://jmettraux.wordpress.com/
yes, discussing it at :
http://groups.google.com/group/openwferu-users/browse_frm/thread/2e8d8a82b87ec11f
Glad to team with Orlin on that.
I've just joined this list, hello everyone, nice to meet you.
Cheers,
John -- http://jmettraux.wordpress.com/
Reply all
Reply to author
Forward
0 new messages