actually  asp and PHP always ran as a separate cgi process because they
were always executable or ISAPI, but before the days of application pools,
they were not as isolated as they are now. CF 1 - 5 were the same too as it
was writen in C language and also ran as a cgi process.
The main issue was people not knowing how to setup websites properly and
tune the settings and security, most folks back then (including me) would
just create a site using the default method and settings, which was not
very secure.
Back in those days ASP was for Windows and PHP was for Linux and CF was far
more RAD than both of them.


On Fri, Oct 3, 2014 at 10:36 PM, UXB Internet <[email protected]>
wrote:

>
> >  explains the problems with CF on shared hosting:
> >  http://www.michaels.me.uk/post.cfm/why-coldfusion-railo-are-not-
> >  suited-to-shared-hosting
>
> Interesting article and a nice refresher for anyone running a shared
> hosting
> environment.  It goes to show how the technology has changed over the
> years.
> In 1998 when I started in this business the best solution for a shared
> environment was CF because ASP and PHP were not very stable and the web
> servers of the time forced them to run in context with the single web
> server
> process.  Therefore a failed ASP or PHP page could easily lock the entire
> web server whereas with CF running out of context as a service if bad code
> caused CF to lock HTML pages would still be served.
>
>
> Dennis Powers
> UXB Internet - A website Design and Hosting Company
> P.O. Box 6028, Wolcott, CT 06716 - T:203-879-2844
> W: http://www.uxbinternet.com
> W: http://www.ctbusinesslist.com
>
>
>
>
> 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:359406
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to