I would definitely agree with a reactor lite. On two projects where reactor was used heavily, we decided to not use the queries because sql was just as easy to write and understandable. Plus the overhead of transforming the objects into query wasn't really much of an advantage.
What I like most about reactor is the crud capabilities. I like the division of gateways from records too. On Mon, Apr 21, 2008 at 4:58 PM, Dominic Watson < [EMAIL PROTECTED]> wrote: > >'m still looking for a PM for reactor who can guide new development, if > > anyone wants to volunteer. > > Quite possibly. I'm highly motivated and good with people (I think) - > I also understand code and application design outside of the trees. > Not sure if that is qualification enough but I'm willing to put myself > forward. > > A few things I have contributed till now: > > * http://fusion.dominicwatson.co.uk/2008/04/scatting-with-coldspring.html > (possibly radicallising aop in ColdSpring for next version) > > * http://betterxml.riaforge.org > * http://betterautosuggest.riaforge.org > > > Dominic > > -- > Blog it up: http://fusion.dominicwatson.co.uk > > > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > -- -- > Reactor for ColdFusion Mailing List > [EMAIL PROTECTED] > Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- > -- -- > > -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [EMAIL PROTECTED] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
