Hi, I have been slowly coming up to speed on Turbine. I am now designing my own application and am searching for the right persistence design approach. There seem to be three options suggested by existing Turbine code. 1. Use the Peer approach used within org.apache.turbine.om.* This uses village. 2. Use the OPaL, which seems to be much more sophisticated but which I understand is incomplete. OPaL does not use village. 3. Use village and JDBC without having a Peer for each major object. This seems to be the approach taken by Jyve. Any recommendations? Stephen ------------------------------------------------------------ To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
- Re: What persistence framework recommended for Turbine apps... Stephen Adkins
- Re: What persistence framework recommended for Turbine... John McNally
- Re: What persistence framework recommended for Tur... Stephen Adkins
- Re: What persistence framework recommended for... John McNally
- Re: What persistence framework recommended... Scott Tavares
- Re: What persistence framework recommended for... Scott Tavares
- Re: What persistence framework recommended for Turbine... Dave Bryson
- Re: What persistence framework recommended for Turbine... jon
- Re: What persistence framework recommended for Tur... Stephen Adkins
- Re: What persistence framework recommended for... John McNally
- Re: What persistence framework recommended... Dave Bryson