[My first vote... can I even vote? I do have commit rights.]
> #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
> #2. Do it inefficiently and not very cleanly. In other words,
> write a services
> wrapper around the DB stuff and then execute that wrapper in
> order to not only
> provide a services arch around the DB stuff, but also to
> provide the destroy()
> functionality without breaking anyone's code.
-1
> > Second, regardless of the answer to the first question,
> shall I commit
> > the destroy() chaining (Turbine servlet's destroy() method
> iterates its
> > Services, calling destroy on each)?
>
> +1 from me, but you need two more.
+1
> -jon
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
