On Tue, Jun 9, 2009 at 8:29 AM, John Mettraux <[email protected]> wrote:

>
> Hi List,
>
> I've been working for a few weeks on a rewrite of Ruote. It's starting
> to take shape, so I wanted to notify you guys.
>
> It's currently at http://github.com/jmettraux/ruota/ but I'll probably
> move it to the proper ruote repo soon.
>
> It aims to have an API similar to the current Ruote one. Process
> definitions will be mostly identical (I want to leverage tools like
> ruote-fluo). The biggest difference comes for the ruote class
> namespaces. Things are moved from the module OpenWFE to the Ruote one.
>
> As it's a rewrite, I was able to simplify a lot of things, and reach a
> better level of elegance/consistence.
>
> The workqueue is by default the traditional Queue one, but there is a
> new one,  which is EventMachine based :
>
>
> http://github.com/jmettraux/ruota/blob/master/lib/ruote/queue/workqueue.rb
>
> Things that are currently missing / to be done :
>
> - concurrent expressions
> - DB / Tokyo Cabinet persistence port
> - sleep / when expressions
> - advanced participants
> - expressions about tags
> - XML 'parser'
> - ... http://github.com/jmettraux/ruota/blob/master/TODO.txt
>
>
> Kenneth,
>
> I'd suggest you focus on this ruote 2.0 for ruote-kit. Wdyt ?
>

Looking forward to it! My last roadblocks on daemon-kit is out the way so
I'll start within the next day or two. I'll announce the repo here as soon
as it's on github as well. Will probably be a rough first week or two.

I know we discussed this in #ruote, but let me know when the external
participants in ruota is ready so I can extract the Nanite, XMPP and AMQP
participant/listener pairs into seperate gems, helping to keep the core nice
and simple.

Just thinking out aloud, shouldn't the DB/TC persistence also be seperate
gems?

Best


-- 
Kenneth Kalmer
[email protected]
http://opensourcery.co.za
@kennethkalmer

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to