On Tue, Apr 6, 2010 at 8:40 PM, Asier <[email protected]> wrote: > El 06/04/2010 13:36, Torsten Schoenebaum escribió: > >> You don't have to use the participant registration method of RuoteKit at >> all. If you like to register participants dynamically, call the engine's >> registration method for yourself and don't use rk's convenience wrapper >> (the call should be something like >> RuoteKit.engine.register_participant participant_name, >> participant_class_or_instance, additional_args >> ). >> >> RuoteKit is just a wrapper to Ruote, it's perfectly well to use Ruote's >> methods directly. RuoteKit's power lies then therein that it provides >> you with a singleton method to access the engine (via RuoteKit.engine). > > Yes, but I think that will only work if I'm developing with Ruby and have > access to ruote internals, but if I'm working with an external application > (c#, java) I can't "interface" with Ruby, so there's the need for ruote-kit > and it's REST interface.
Hello Asier, hello Torsten, it depends, you can have [ruby] participants that call services written in any language. The communication could occur over HTTP, SMTP, AMQP, whatever. You can think "pull" as well as "push". If you want to pull from ruote, then maybe yes, you would need the rest interface. Many possibilities. Best regards, -- 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 To unsubscribe, reply using "remove me" as the subject.
