On Tue, Apr 6, 2010 at 11:46 PM, Torsten Schoenebaum <[email protected]> wrote: > Asier schrieb: >> El 06/04/2010 14:23, John Mettraux escribió: >> >>> Quick note. >>> >>> With some storage implementations [1], it's possible to [un]register >>> participants directly (without passing by the Ruby ruote classes). >>> >>> For instance, if you use the Ruote::FsStorage implementation, you can >>> locate the file participant_list.json and modify it (better lock the >>> file during the manipulation, else the engine might cough on >>> half-written content) with any language/tool that understand locks and >>> JSON. >>> >>> >>> Best regards, >>> >>> >>> [1] http://ruote.rubyforge.org/configuration.html#storage >> >> Oh! This could be great! Does this approach work with DataMapper >> participants?
Yes, it works with Ruote::Dm::DmStorage. > Disclaimer: This is *really* advanced stuff and may break if future > ruote versions change the way the participant_list is stored in > (although I don't suppose that John has any plans to do so). True. > I'd advise you not to use that 'feature' unless you know what you do and > have good reasons not to use the 'standard' api. As I don't know your > intentions, I can't answer that question for your use case: It may be > worth a try, but most probably it won't. Torsten's proposal of using a "catchall participant" is probably the best one so far. We're just firing suggestions at you without knowing your context / requirements. We're eager to show the flexibility of ruote (and Ruby). Maybe we (especially I) had better shut up and only try to help you when you have more precise questions. 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.
