Hi guys, I could have done my research a little better. Kenneth's ruote-kit seems like exactly what I'm looking forward to.
Hooks are in the nature of ruote's "real" / external participants, aren't they? With ruote-kit being a restful http service we've got the http-in. Shouldn't it be able to http-out as well? Without requiring a ruote-http gem (the non-proliferation point). It seems to me ruote-kit is going to be fit for webhooks anyway :) Wouldn't you want priority for the workitems? Perhaps a couple of queues - one for _asap_ and one for _whenever_. Some protocols and type of use (e.g. XMPP or AMQP) may often need better response time than let's say email notifications, but explicitly requesting it could be part of the DSL. Perhaps several levels, because it could be something people pay for - priority processing for whoever needs / deserves it most. And if ruote2 does have to be polled, it could be done with ruote-kit rather than yet another layer (e.g. ruote- hooks?). Enentmachine is already required by daemon-kit... You are probably much better informed than me, but I'll mention a couple of libs just in case. As far as the http calls - there's http://github.com/pauldix/typhoeus - to make things less blocking... And for storage, we could use http://github.com/wycats/moneta (that also speaks tokyo among a wide variety of stores) - is just a hash good enough? Reading through ruote-kit's notes, let me ask about a couple of points. Isn't rails already on rack and if so what's the "complementary" gem for hooking into rails about? Also: completely restful, but without all the lingo? Thanks for the flattery about being smart. I don't think I'm as smart as you, certainly less experienced. I just have a use case, using ruote for hooks, and don't know what "walking the last mile" would be like. Seems like you plan to walk it anyway ;) I'm not in a big hurry. I could use a development version in September / October. Planning a production release for December. Something caught my eye though, in the ruote-kit notes again, that I could contribute to. A site to share process definitions. It can also be a store to sell or rent process definitions that hook into 3rd party services. The webhook extensions / plugins. Something that combines with ruote-kit and makes processes available based on openid, oauth, etc. I feel more capable of doing this than messing with ruote's internals... Best, Orlin --~--~---------~--~----~------------~-------~--~----~ you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
