As far as rewriting techniques, there are ways of doing partial rewrites
and slowly taking over the site section by section.
Rewriting the CF is relatively easy. Few sites have enough of a line-count
(at least not a justified line-count) that would make the coding that time
consuming. Usually the fixes involve taking out repetitive code blocks and
replacing them with includes/modules/CFCs so that's not that hard.
What takes the most time is changing the db schema and the queries. In
fact, this is usually the deal-breaker since you usually have to get a dba
involved to preserve the legacy data. This is not trivial if you have very
active tables with millions of rows. Good luck getting any planned
downtime for this.
So I've always spent most of my development effort on the database design,
knowing that this is the most inflexible part of any web application. Then
if I have to rush through the CF, so be it. It can get rewritten later.
The db design is also usually your main performance bottleneck. A good db
design can keep a site running sloppy CF running better than optimized CF
running against a cruddy db design.
At 05:54 PM 4/30/2005, you wrote:
Any thoughts to the best way to slip managed code and
best practices under the covers of an already poorly
written site when you don't have the luxury of
altering the whole thing.
~|
Logware (www.logware.us): a new and convenient web-based time tracking
application. Start tracking and documenting hours spent on a project or with a
client with Logware today. Try it for free with a 15 day trial account.
http://www.houseoffusion.com/banners/view.cfm?bannerid=67
Message: http://www.houseoffusion.com/lists.cfm/link=i:11:2502
Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/11
Subscription: http://www.houseoffusion.com/lists.cfm/link=s:11
Unsubscribe:
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.11
Donations Support: http://www.houseoffusion.com/tiny.cfm/54
