>> I've recently discovered that IE & Netscape have a lot of rather major >> differences in the way they work. Server based code (that doesn't really >> do anything that *SHOULD* be browser specific) behaves radically different >> with the various different browsers. >And that ridiculous behavior is going to be the death knell for JavaServer >Pages. Since you can't count on even your basic HTML working correctly, >that means that you're pretty much going to have to generate nearly >everything on the fly in a servlet. I agree that it's a pain in the rear end, but it ain't the end of the world. There's still plenty of scope for browser-neutral JSP code, and that's what many people will aim for. And I don't understand the comment about servlets -- if you can solve the problem in a servlet, why can't you solve it in JSP? Or in a system that combines servlets and JSPs? +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: firstname.lastname@example.org +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.