james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Charles Benett <char...@benett1.demon.co.uk>
Subject Re: Town replacement
Date Tue, 08 May 2001 15:20:24 GMT


Steve Crossan wrote:
> 
> > I can think of four alternatives for db support in james: town, jdbc,
> > avalon, turbine.
> >
> > 1) Stick with town.
> >    Pros: (per serge) Abstraction across multiple drivers, simpler than
> > JDBC, connection pooling
> >    Cons: (serge) forces message instantiation
> >          (charles) how active is the town community?
> 
> seems quite inactive recently - but we could reactivate it :). It would be
> great to have a good open source Object-Relational mapping solution and
> Town seems to be a good start - I don't know how far the other projects go
> down that route.
> 
> > 3) Avalon (jakarta)
> >    Pros: provides pooled connections,
> >    Cons: don't know much about this, possibly limited community at
> > present (Avalon & cocoon)
> >
> > 4) Turbine (jakarta)
> >    Pros: provides pooled connections, Peer object (OR mapping)
> >    Cons: don't know a lot about this, either!
> 
> Turbine seems to be the best supported right now. Possibility - merge Town
> and Turbine - i.e. take the OR Mapping stuff from Town and move it into
> Turbine? Anyone active in the Turbine lists?

I've only just started with Turbine, hence not up to speed. But the Peer
classes and torque may do the trick.

Charles

---------------------------------------------------------------------
To unsubscribe, e-mail: james-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: james-dev-help@jakarta.apache.org


Mime
View raw message