The paragraph is correct. You can write a presentation layer in ASP.NET with absolutely zero application logic. All the time. With no exceptions.
This still isn't possible in CF, or JSP, or ASP, or PHP, etc... ----- Original Message ----- From: Mike Brunt <[EMAIL PROTECTED]> Date: Thursday, July 17, 2003 10:07 am Subject: RE: MSDN on CF -> ASP.net > I'm on my way out so can't read all, but paragraph 3 deserves some > kind of > response: - > > "ColdFusion follows the same development and page execution model > as that of > classic ASP, PHP, JSP, and other similar Web-scripting languages. > Specifically, code is embedded in HTML markup, and as a given page > executesfrom top to bottom, the output of the code's execution > takes the place of > the embedded code in the resulting HTML document. This development > model is > easy to grasp, but it does have a number of drawbacks. Chief among > these is > the lack of separation between application logic and presentation > markup.Mixing code and presentation makes the code harder to read, > which increases > the time and effort involved in maintenance, and creates significant > challenges for non-programming graphic designers who need to > modify a page. > Over the years, ColdFusion has introduced several ways to mitigate > this lack > of separation, including custom tags, and others-but the > fundamental model > remains." > > What about cfc's and for those who really want to move more OO > concepts CF > and Mach II. This is typical MS BS and deserves a response from > MM in my > opinion. (A lot of bloody abbreviations there!). > > Kind Regards - Mike Brunt > Webapper Services LLC > Web Site http://www.webapper.com > Blog http://www.webapper.net > > Webapper <Web Application Specialists> > > -----Original Message----- > From: Jesse Houwing [EMAIL PROTECTED] > Sent: Thursday, July 17, 2003 8:44 AM > To: CF-Talk > Subject: MSDN on CF -> ASP.net > > First it explains what both ASP.net and Coldfusion are and that > they share a > similar background. A simpel feature comparison is used to show > how one can > convert a Coldfusion Application to ASP.net. > > It contains a few errors, especially 'forgetting' to mention that > a lot of > functionality is available in the standard JAVA API's which van be > directlyaccessed from coldfusion (Image support in ASP.net is also > only available > through teh .Net framework, the same applies to SAX XML support and > Threading). > > They conclude that ASP.net is more reliable, faster scaling better > etc. etc. > without showing any figures ro numbers. > > Read it for yourself: > > http://msdn.microsoft.com/library/default.asp?url=/library/en- > us/dnaspp/html/coldfusiontoaspnet.asp > > Jesse > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
