Hello, I have a question/clarification about the HistoryStorage participant. There is a comment in the documentation here:
http://ruote.rubyforge.org/rdoc/Ruote/StorageHistory.html "Note that, by default, the history is an in-memory history (and it is useless when there are multiple workers)" 1.) I assume that the multiple worker comment does not apply since the history is persisting in storage. is this correct? 2.) Our workers get started via a daemon, we are also using ruote- sequel and Ruote-kit. When we try and call RuoteKit.engine.add_service( 'history', 'ruote/log/storage_history', 'Ruote::StorageHistory') It does not seem to properly register the service or the service seems like it is getting overwritten by the DefaultHistory.The context.notify never calls StorageHistory.notify. But I have seen the service gets registered. When I add the service via Ruote::Context.default_conf everything works correctly. Should the service be register from the worker or when the engine is initialized or both? I have tried both with no effect. I had not noticed the service architecture before. Very cool. Thanks Eric -- 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
