|
> From: Walden H. Leverich > > As for ease of development -- I'm sure this will start a war -- but I've > found ASP to be extremely easy to learn. I think the war has cooled down over the last year or so, Walden. ASP is easy to use. It's MS specific, but these days that's not a huge issue. It's just one you have to be aware of. I prefer JSP because done correctly they really fly - once the JSP is compiled, it's basically sitting in memory and spinning out data. Of course, you can mung it up with a bunch of junk, but you can do that with ASP too. JSP, however, requires at least a little Java knowledge and a servlet engine. And the loading of the data is (usually) on the host. I forget how exactly ASP s traslated - it's all in the browser isn't it? If so, that means a lot of load on the client, but personally I kind of like the idea of making the client do the work. Then again, a properly designed JSP implementation can have the web server on a separate box than the business logic. I have one client using Tomcat on FreeBSD calling redeployed RPG programs on their AS/400. The 400 is now entirely batch, with no WebSphere overhead. In any event, I think the deployment language is a matter of personal preference. As long as the architecture separates the UI portion of the deployment from the business logic (be it through stored procedures, sockets or data queues) then I'm happy. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.