This is a tough question. How is the current application architected? Is it all CFC based, custom tag based, queries in the beginning of display files? queries scattered around various files, etc?
If they are queries scattered around various files then I would probably just pick a section of the site and start from there working my way though one section at a time. If you are in a more object oriented design and have DAO's currently defined then I would start with one DAO and work on phasing it out, refactoring your code where necessary to take advantage of Reactor's added functionality. Bill On 3/19/06, Brad Haas <[EMAIL PROTECTED]> wrote: > I'd like to get some thoughts about how I would go about gradually > integrating Reactor into an existing production web site. I know > there are probably not a set of best practices yet, considering > Reactor is in a beta state. > > I have a copy of the existing site on a dev server and I will test > changes there and roll them out, but I plan to roll the changes out > over time instead of having one big revision release. Anyone have a > method or process for doing this? It may as simple as updating the > Reactor files, but I just want to make sure that I'm not missing > anything. > > Thanks, > Brad > > > > > > > > -- Reactor for ColdFusion Mailing List -- [email protected] > -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/ > > > -- [EMAIL PROTECTED] http://blog.rawlinson.us If you want Gmail - just ask. -- Reactor for ColdFusion Mailing List -- [email protected] -- Archives at http://www.mail-archive.com/reactor%40doughughes.net/
