I used to do a lot of ASP work, have since switched to JSP and have never looked back. I like the technology much better and I'm always going to be a bigger fan of an open spec rather than a closed one. However, if your system works, it may be beneficial just to roll with it. If ever reach the point where you're going to be doing a major overhaul, that might be a good time to look at an alternate technology. But, as they say, if ain't broke... Darin Wilson [EMAIL PROTECTED] http://www.doughnet.com/ -----Original Message----- From: Fred Durham [mailto:[EMAIL PROTECTED]] Sent: Monday, October 11, 1999 9:35 AM To: [EMAIL PROTECTED] Subject: Brutal opinions requested We currently do all development on IIS using ASP combined with ActiveX on the server to do what ASP scripts cannot (like beans I think), and ISAPI when ASP just can't do what we need. JSP looks really tempting. Object based (unlike ASP and VBScript), one language (Java) right now we keep 3 code bases - ASP, ActiveX + ISAPI projects. However, we know this windows centric system works, and switching is a risk (though, as I say, a very tempting one). Bugs, down-time, random crashes, weak class libraries, etc are all big problems for us. * Any brutally honest opinions about the state of JSP is *greatly* appreciated. * Any pointers on which vendor to use for the JSP environment to run in? * Where's it fail? Given the choice, would any of you rather use a different technology? Thanks! -Fred =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". FAQs on JSP can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". FAQs on JSP can be found at: http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.html
