Hi,

ruote 2.1.8 just got released.

Here is the changelog :

---8<---
- participant#schedule_timeout workaround for issue with JRuby 1.4.0 (1.8.7)
- implemented Ruote::CompositeStorage
- leveraging rufus-cloche 0.1.16 and the 'cloche_nolock' option (FsStorage)
- SmtpParticipant and ruote/part/template.rb reorganization
- StorageParticipant when returned by engine#register was unusable. Fixed.
- string keys for SmtpParticipant. Thanks Gonzalo
- fixed every('10m') bug. Thanks Gonzalo Suarez
- Ruote::FlowExpressionId.from_id(s) more permissive
- concurrence (and concurrent-iterator) :merge_type => :stack
--->8---

Here is the changelog for ruote-couch 2.1.8 which got released as well :

---8<---
- 'couch_timeout' configuration parameter
- 'couch_prefix' and :prefix as configuration parameter
--->8---

Here are explanations about some of the changelog items :


== couch_timeout

up until now, ruote-couch was very naive, it was polling at least
twice per second couch for incoming msgs (internal tasks). Since
ruote[-couch] 2.1.8, it's using long polling.

see 
http://groups.google.com/group/openwferu-users/browse_thread/thread/37de357b424c4405
for more.


== concurrence :merge_type => :stack

This is a new kind of merge for "concurrence" and
"concurrent-iterator". The documentation is at :

  http://ruote.rubyforge.org/exp/concurrence.html

It's a more natural way of gathering the workitem payloads (fields)
when merging concurrent branches.


== a few mini fixes for ruote on JRuby

There were a few glitches with ruote on JRuby in the test suite. They
should be fixed by now.


Many thanks to Gonzalo Suarez and Francisco "Kiko" for their active
issue reporting, and to Torsten Schoenenbaum for all his work with
ruote-kit and http://github.com/tosch/ruote-on-rails

-- 
John Mettraux   -   http://jmettraux.wordpress.com

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