On Sat, Feb 28, 2009 at 11:54 PM, bokmann <[email protected]> wrote: > > My railsconf talk on Workflow has been accepted: > > http://en.oreilly.com/rails2009/public/schedule/detail/7535 > > Hope to see you guys there!
This is great. I especially like the "whole span" approach you're taking. Looking forward to see the slides and the video. If you need any help, please ask. One major drawback of ruote "on Rails" is that, since it requires threads for its workqueue, it can't work on passenger for instance. Multi process mongrel packs require tweaking. It's not a big problem for small company deployments, but the tendency in the Rails world (as you know) is to "scale somehow", so :( One option is ruote-rest behind the Rails application. We were discussing that with Kenneth (he's using ruote[-rest] to drive DNS provisioning flows), that's his solution : ruote-rest behind. There'll be a convergence between ruote and ruote-rest in the future. ruote-web2 will then work with ruote embedded (single process) or with an 'external' ruote[-rest]. OK, just wanted to underline those issues (especially since you'll be mentioning ruote in your talk). Congratulations !! -- 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 -~----------~----~----~----~------~----~------~--~---
