On 13 nov, 02:04, John Mettraux <[email protected]> wrote: > "ruote as a server" best incarnation is currently > :http://github.com/kennethkalmer/ruote-kit > > the 'client' application communicate with it over HTTP. Usually it's > JSON over HTTP. > > Launching a flow implies POSTing a launchitem encoded as JSON to a > /processes resource. While browsing the workitems currently available > for a participant is done by GETting /workitems/participant_name.
Ok, so with ruote-kit I can remotely manage ruote. Great. > The Abstra.cc guys are running a ruote-kit equivalent in JRuby. From > it they can access various Java libraries directly and other > applications can talk over HTTP to the application. > > (Abstra.cc please correct me if I'm wrong). Is this Open Source. > I've seen other people communicating with remote ruote via DRB (some > kind of Ruby RMI). > Ruote doesn't do any user/role management. It only has some > participant name/regex to participant implementation mapping. > > Sorry for the fuzziness of my answer, best regards, So ruote only takes care about worklow, leaving role/participant management to external applications. That's fine. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
