Just to be clear -- I like REST, but I chose it for Fluxr not because I really want a REST interface for OpenWFEru, but because I needed a platform-independent network interface for the engine, and I don't like XML-RPC and SOAP.
My main goal with Fluxr though is to provide a simple, slick front-end for managing the OpenWFEru engine. That's it. The fact that the REST interface combined with ActiveResource makes Fluxr potentially fit into a greater enterprise-ey Ruby scheme is just a bonus (albeit a really nice one). On 8/29/07, John Mettraux <[EMAIL PROTECTED]> wrote: > > Hi Pat and Matt, > > > http://gilesbowkett.blogspot.com/2007/08/activeresource-rails-scalability.html > > Interesting blog post. > > Seems like both of you would like to have an OpenWFEru engine and > worklist wrapped within a RESTful container... > > > Best regards, > > -- > John Mettraux -///- http://jmettraux.openwfe.org > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenWFEru dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/openwferu-dev?hl=en -~----------~----~----~----~------~----~------~--~---
