JSP vs ASP vs Cold Fusion ???

For development of jsp-pages you can use Jrun free licence version, or J2EE
from Javasoft. Or TomCat from same place.

Unfortunately, I agree that with Microsoft you can develop ASP and serve
ASP on products without buying anything more than the NT server. With jsp
you can develop for free - but I haven't found any free solutions for commercial
robustness and business use yet. ASP could be thought as one, although you
do have to buy Windows.

I have no experience of non-windows asp platforms, but I've never heard of
anyone using them in actual production either.

>3) jsp servers ARE RARE species as yet now (hunting for whole good one month)
>i haven't found a descent server that can be obtained as shareware or freeware
>on which i can even BEGIN experimenting!! otoh PWS for win98\95 and IIS
4.0
>for NT and IIS 5.0 (fundoo server) with win2K (a really groundbreaking os)
>comes bundled with their respective OSs and are perfect with asp.

I agree with this. Writing too much script code on the page leads to limited
resuse and very tough to maintain. I've seen this in both ASP and JSP.
No matter what your server side processing technology is; COM, SSI, servlets;
you should always stay away from page scripting unless you're building a
small site.

I still believe Microsoft and ASP are far more advanced at this time, for
both simplicity and scalability. However, I do believe Java and JSP are
gaining quickly. Since VB is not an proper OO language, your back end design
is hindered because of this. And since COM is limited in it's design capabilities,
Java is a far superior OO modelling language. Granted, with the changes
to VB 7, it could be an exciting race. I think it all comes down to personal
preference. It's a tough one to dispute.

I'm not too familiar with CF, but from what I understand, it's a quick and
dirty solution. Basically, for people building non-scalable sites.

Gary

"Sebasten Bouchet" <sebastien.bouchet@lycosmail.com> wrote:
>
>You have to analyse whch amount of extra service you need. If you want email
>capabilities, ldap support, a naming service, platform-independant DB access
>and growing XML support, then Java (J2EE)is a good think to look at.
>
>Then keep in mind that ASP runs best on Microsoft platforms (in spite of
>Chili software), Java technologies on Unix machines, especially Solaris.
>
>But to me, both ASP and JSP (I don't know about CF) fail to separate business
>logic from presentation by allowing web authors to embed far too much code
>in their pages.
>
>I'm convinced that the only safe way to use JSP is too use them along with
>servlets. The functional paradigm then becomes :
>1) Intercept the client request with your servlet, process the data and
business
>logic (db access, online pricing ...)
>2) Forward the results to your JSP which is clearly devoted to presentation
>and presentation only, with JSP tags containing little code.
>
>By doing this your Java code is cleaner and can be as complex as you want
>it to be (add exception handling to your JSP code and have a look at your
>document in Dreamweaver ...)
>
>Hope this helps understanding what your needs are
>
>Sebastien

"Andi" <annops@hotmail.com> wrote:
>
>Hi All,
>
>Have anyone have an experience with ColdFusion? I read all your discussion.
> I just only ASP vs JSP.
>
>Thank

Asking which tool is better is like asking which ice cream flavor is better:
It depends!

We use both ASP and ColdFusion in our shop. Choosing a tool depends on what
the client wants, what platform(s) the code will be running on, and which
developers I have available for a project!

ColdFusion is tag-based, so our HTML developers have really embraced it as
something "close" to what they're used to. Our VB- and Access-experienced
programmers prefer ASP (but they also "do" CF, so they're my "utility infielders").

ColdFusion is really good for quick development of an application (we recently
finished a 300+ module CF app in ~5wks), but ASP is better for more involved
business logic and native (ADO) connections to SQL Server. ASP is better
for more "traditional" programming styles, but CF is better for those not
wanting to get bogged down in programming details. ASP is better for accessing
files and folders on a server, while CF's CFCONTENT and CFFILE tags are draconian,
to be kind.

HTH,
Andrew Cooper
Partner/Chief Technologist
Interactive Business Solutions, Inc.
http://www.n2biz.com