Hi, I am also +1 for the full decoupling of services including security with decoupled Torque. I have avoided migration for my app having seen the sheer volume of questions on this 'problem' on the mailing list.
I think Turbine User list consumers (being capable techno types) would appreciate this:- http://members.lycos.co.uk/neilgibbo/work.swf David -----Original Message----- From: Martin Poeschl [mailto:[EMAIL PROTECTED]] Sent: 09 July 2002 17:54 To: Turbine Developers List; turbine-user Subject: [vote] Turbine 2.2 release Turbine 2.1 was released more than a year ago. I think it's time for 2.2 ;-) status: 2.2-dev works with the decoupled version of torque except for the security service. 2.2-dev works with some parts of fulcrum (i'm using fulcrums xml-rpc service) plan: *) change the security service to use the decoupled torque and remove the coupled version + the coupled version has some problems which are fixed in the coupled version + the coupled version is unmaintained + it will be easier to change to turbine-3 - this will brake backwards compatibility!! (package names, Vector -> List) <quote> FYI, the List->Vector change in Scarab only took me about an hour total, so, for those of you waiting, it won't be that bad of an upgrade. -jon </quote> :-)) *) leave the services as they are (at least for turbine 2.2) - it would be hard to make turbine 2.2 work with fulcrum - *) release Torque 3.0-b3 and Turbine 2.2-b2 by the end of the week *) release Torque 3.0 and Turbine 2.2 2 weeks later (26th july) (or Torque b4 and turbine b3 .. depends on feedback) i x-post this mail to get additional feedback from the user list :-) martin -- 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]>
