There is no solution! T3 continues to use the embedded user/security stuff. Which is great if the default turbine user and security is what you want, but if you want to drop in your own user/security stuff, then it doesn't work very well.. Pluggable user/security is something that comes up, and then dies away... As far as the decoupled versus coupled torque issue, I am not real sure.. Scarab drives a lot of the T3 requirements and development, and I would look at cvs and scarab to see..
Eric -----Original Message----- From: Anthony W. Marino [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 18, 2002 10:56 AM To: Turbine Users List; Eric Pugh Subject: Re: turbine 2.1 or 2.2 > My 2 cents is that 2.2 is much better then 2.1 because of all the bug fixes > (especially in the decoupled torque) EXCEPT for two things.. If you need > to have users and security, and you want to use the decoupled torque, then > you end up with two different ways of accessing the database... All your > application code can use the decoupled torque, but all your security/user > code needs to use the coupled torque code. However, if you are rolling > your own security, or user stuff, then definitely go with 2.2. > What are the security solutions with T3? > Having said all that, T2.1 is released, T2.2 is beta, but all the interest > is T2.2. Also, have you looked at scarab? scarab.tigris.org is based on > the T3 stuff and it seems pretty stable. > > Eric > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 17, 2002 12:38 PM > To: [EMAIL PROTECTED] > Subject: turbine 2.1 or 2.2 > > > Hello folks, > > I'm new in the world of Turbine and I want to install it on my development > environment. > > But can I install the next release, 2.2? Is it stable and ready for > production? > > Thank you > Sylvain -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
