Ok -
First of all, it sounds like your customer knows what the problem is. He
has a contactor that isn't delivering what he promised.
Second...the ASP developer's 'excuse' is pure rubbish. Whatever ASP/CF
interaction there is you have explained (Processor, DB, etc)...and these are
not the problem! The problem is a slow developer. Including your CF code
on his server isn't going to magically start making his development faster.
The problem right now is that he isn't fast enough. How is it going to make
it faster if he is the one to migrate the CF in addition to what he does
now? Does your customer want to start seeing the same response time on the
CF code?
It is absolutely unreasonable to ask you to turn source code over to a
competitor.
I think the prime question to ask is "How is this going to make his
development faster?" His answer (eliminate bugs in the ASP code) will show
a total lack of technical expertise. I'd begin by making sure the customer
is educated about the limits of ASP/CF interaction.
Finally...if you can handle it...make an offer to take over his development.
Along the course of new development, include re-writing his ASP into CF.
With the rapid development time of CF, you should be able to write new
functionality, convert his code AND do both quicker than he wrote it the
first time.
Brian
-----Original Message-----
From: Mike Kear [mailto:[EMAIL PROTECTED]]
Sent: Sunday, January 28, 2001 9:47 PM
To: CF-Talk
Subject: Politics RULE - GRRRRRRR
Guys, I have a political problem here and I'm looking for ammunition. I
want to head off this problem before it causes me damage ....
I share a site with a competitor who is doing a lot of ASP work on my
client's site. I do a whole lot of ColdFusion work and we're supposed to be
working together. For 15 months we've had no problem. We've kept the two
parts of the site separate and they don't get in each other's way except to
share some processor time, disk space (I keep all the CF stuff in my own
folders away from their work) and SQL Server processing time. (I have my
own databases in SQL so they don't get in the way either).
Suddenly, the ASP developer is under pressure for non-performing work -
unless he does something dramatic, he's about to lose his contract, and is
looking for a way to dump the blame on me. (My client doesn't think he's
done much of a job at all, but he's had the lion's share of the dollars so
far so he has to at least pause to listen to what he's told.)
The ASP Developer's strategy is to whine that their development server isn't
an exact copy of the live server. (It hasn't been for 15 months - they
didn't even realise there was cold fusion on the live server.)
So they want me to put all my ColdFusion templates on their development
server instead of the live server and they'll load them onto the live
server for me. (Ahh!! how nice of them!) They're saying that this will
enable them to verify that my templates aren't going to impact negatively on
their work or cause undue cycles on the processor, or hinder the SQL server
handling their calls. They want to put (get this!!....) Front Page
extensions on their development server, so it can handle the deployment of
my ColdFusion work up onto the live site.
A little about my work for this site ... its predominantly built using ASP,
which builds flat files from the SQL Database once a day. So the site has
1500 or so flat files, plus another few hundred pages drawn as pay-per-view
pages from the SQL Server. My ColdFusion work is a whole series of small
stand-alone applications, consisting mostly of SELECTS and display tables
from small tables. They have no session variables, application variables
etc except for an admin area to update the tables that might be used by one
person for a day or two a month. In terms of page views, the ColdFusion
would amount to a maximum of 20% of the overall traffic.
I build on my local machine, test using a duplicate of the SQL Datasource,
then deploy data and templates to the live server.
What I need is reasons why the ASP Developer ought not to have my templates
on his server first. I know the REAL reason is so he can chip away at my
credibility by picking fault with my work, but of course that's not how it's
going to be presented to the client. I don't want a competitor approving my
work before it gets deployed.
Cheers,
Mike Kear
AFP WebWorks,
Windsor, NSW, Australia
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
