on 1/30/01 7:12 AM, "Santiago Gala" <[EMAIL PROTECTED]> wrote:
> I imagine that we will converge eventually towards Avalon. I expect this
> to happen, so that we can merge freely turbine services, cocoon
> services, etc. I have read that you are considering this for turbine
> once it is released, and I think this is a move in the right direction
> for everybody, as we will have better use of our developer base if
> services are maintained for several projects together.
Nope. We aren't moving to Avalon at this point in time. There isn't a need
or a close fit yet (that I can see) and converting Turbine to use Avalon
would require more API changes to Turbine than I am willing to submit people
to at this point. Again, I just don't see where the two fit together. I can
see Avalon being used as the basis for Tomcat, but I don't see how it would
be used as the basis for Turbine...even the services architecture.
My suggestion to you is to use Turbine Services for singleton objects
primarily because you already depend on Turbine and it offers this for you
in a very clean fashion. Adding another dependency (ie: on Avalon) in order
to get any duplicated functionality is a bad thing.
That said, I'm -1 on using Avalon for providing services in Jetspeed. It
just isn't the right fit IMHO.
-jon
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
