on 3/23/00 8:52 AM, george stewart <[EMAIL PROTECTED]> wrote: Hello George, welcome back. Long time no see... > I suggest adding a service manager, and implementing > something like cocoon's manager. In cocoon, there's > an interface called actor. The manager can create an > instance of an actor. If the actor implements the > configurable interface the manager initializes it. > Each actor has a "role", a name, so you can retrieve > the actor from the manager by name. That is essentially what the TurbineServices already do with a bit more features. I wouldn't mind seeing this added into the existing Services model. > Would it be much trouble to divide data access so > interfaces are in one directory and implementations > are in another? With this approach and some > cooperation from developers, it would be easy to use > ant to build either with or without village. This is already mostly done in the Peer classes... > It would be nice to be able to build turbine without > using village. It's possible now but you have to edit > the code. I don't see the dependency on Village in the Peer classes as a bad thing. I like Village for the things that it is good for (inserts, updates and selects...mass deletes are questionable)...I don't want to see it go away. > I'm willing to provide the code for this. no offense, but how about finishing up what you started before taking on more work...??? namely OPaL...;-) there is zero documentation and working examples for that stuff...also, how complete is that code? ;-) thanks, -jon ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
