I'm not about to say that CF is the "be all - end all"
language, it is not.  I am one of its biggest proponents
in the e3000 realm though, so my view is a tiny bit biased :)
I think trying to compare development times between JSP/CF/ASP/etc
is silly and not really useful to anyone honestly trying to
decide what the appropriate technology is for a particular
application.  That said, developing a web-based application
with CF is probably quicker than a similar application in
many other languages (2-3 weeks versus 6-9 months though seems
like some high pressure sales pitch to me).  That still doesn't
make it the "right choice" for every web-based application though
(ex. If you need to have a totally e3000 platform solution, then CF
doesn't fit the bill whereas JSP can).
  I've chosen CF for several web projects, and have been very happy
with the results (although desperately needing a face-lift, the
www.sambaix.com site is an example of 100% CF code delivering a
dynamic/customizable user interface).  On the other hand, I probably
wouldn't recommend CF as a real-time control langauge ;)

Regards,
Michael L Gueterman
(From the Internet Pavilion at HPWorld!)
Easy Does It Technologies
http://www.editcorp.com
voice: (888) 858-EDIT -or- (573) 368-5478
fax:   (573) 368-5479


-----Original Message-----
From: Cortlandt Wilson <[log in to unmask]>
To: [log in to unmask]
Date: Mon, 11 Sep 2000 14:06:18 -0600
Subject: [HP3000-L] Apache vs. Cold Fusion  (was HPWorld 2000 On Sunday)

> > Cold Fusion is the way to go for webifying your
> > applications.  Although the same work can be done
> > with Apache/iX and CGI scripts it was stated the
> > what takes 6 to 9 months in Apache/iX and CGI,
> > takes only 2 to 3 weeks in Cold Fusion.
>
> I think a far more relevant comparison would be the time difference
> between Java Server Pages on  Apache/iX and Cold Fusion.   Any word
> on
> those numbers?
>
> - Cortlandt Wilson
>   Java Newbie
>
> P.S.   Thanks for the HP World update
>