[EMAIL PROTECTED] wrote:
> #1. Screw things up for people and fix Turbine to do the right thing. Note
> that the DB stuff was done LONG before the Services stuff was, so that is why
> things are screwed up in the first place. Given that we haven't released
> anything as final yet, I'm leaning towards this as long as it can be
> accomplished quickly.
+1
Maybe we could make old DBBroker a wraper class for the Service, to avoid
breaking people's code, and eventualy change references to it throughout
Turbine to use the Service directly.
I must say that as my projects deadlines come closer, I get a bit itchy
about major changes... We'll probably have to freeze our Turbine snapshot
at some date, and proceed very carefully from there on.
Never the less, the show must go on. Work like hell guys and do (and
break) what it takes for Turbine to take over the world! ;))
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
