Hi Tomaso, sorry for my late reply, I was busy releasing 0.9.16 and working on my day job.
On Nov 19, 2007 6:36 PM, Tomaso Tosolini <[EMAIL PROTECTED]> wrote: > Hi, > ...no problem :) i can change it if you think it's better simplify it's > structure... > But please help me to do a summary of the features that can be useful > to one that want's use Rufus embedded in his/her rails app: > > Here are the ones i found useful for me > - creare a single point of connection to the engine and a (very simple right > now) control mechanism for it I think there shouldn't be a facade (connector) in front of the engine. > - integrate the active store participants to have a db persisted engine out > of the box The active store participants have their own persistence which is different from the one you provided for the engine itself. What do you mean by this "integrate" ? > - hide the registration process of the active store participant, because > these ones are the most > important for me because next i want to write the app to process the > items(as obvious) Maybe it could be done like it's done in Densha : at engine startup time, store participants are registered in the engine (that occurs in a configuration file). > - have the ability to access the engine in order to do special work ( in the > future the latter can become a > feature of the plugin or of an its specialization ) Maybe it's related to your 1st bullet point. What do you think ? -- 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 -~----------~----~----~----~------~----~------~--~---
