> I found this article interesting:
>
> http://www.asptoday.com/articles/20000427.htm
That was interesting, but it lead to some concerns. For example, JSPs can
access the database directly, but most large scale applications don't do
this because having front-ends access the database tends to increase the
number of connections to the database and often makes the code a bit less
maintainable since DB logic is spread out over presentation pages rather
than in business logic that is shared, and of course one of the "benefits"
of CF was that people skilled with presentation logic didn't have to worry
about formulating db queries and the like.
Also, CF seems to be directly tied to HTML in that you don't really write
HTML, but instead use a proprietary markup that only Allaire supports.
Since it auto-generates Javascript and these things -- which is very nice
for desktop browser applications I will certainly agree -- it seems like
it's not like JSP in that it may not be able to general XML documents on the
fly (JSPs can basically create any kind of text output file, not just HTML).
Is that true, or just a misreading of a primer?
CF does seem much more mature, with lots of goodies that are only promised
by taglets.
Is there any real-world comparison of CF template processing being faster
than bytecode processing within a JVM? The article states that CF is
faster, but that seems amazing unless CF templates are compiled in native
machine code.
David
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
