In my net-basesd application (heavily on DB record manipulation/display), I use servlet to receive client requests and dispatch requests to various beans for data processing (3 tier and model 2, references -> java.sun.com and www.javaworld.com, www.serverpages.com, www.javadeveloperjournal.com etc). I think XML is good way to pass data. Now I am thinking whether to use JSP/HTML or applet in the client side. Hi, I include part of a post from
another interest list,
maybe you find it interesting or
applicable to this thread:
What I like most about DNA and what I
think J2EE still lags behind is:
+ IExplorer 5 Dynamic HTML clients with XML Data Islands, HTML Data Binding, Remote Data Services and local XSLT support. There is nothing in J2EE as powerful as this combination. With this technology you can implement a DHTML client with database access, data sorting and filtering functions, with about 30 lines of HTML/XML/XSLT/JavaScript code. We are providing solutions to our clients using JSP and cross-browser DHTML and we are severely crippled by not being able to use IE5 non-portable features like the ones you can see at http://msdn.microsoft.com/xml/articles/xml020899.asp http://msdn.microsoft.com/workshop/author/databind/dude080299.asp + ADO 2.1 disconnected recordsets. JDBC looks positively crude compared to this. With ADO things such
us asynch operations, cancel functionality, conflict
resolution, HTML/JavaScript/XML integration is by far better than whatever J2EE provides... well, actually J2EE does not provide **anything** for HTML client-side functionality. Regards
Javier
Borrajo
|
Title: JSP vs Applet discussion
- JSP vs Applet discussion Hu, Jeffery X (Jeff)
- Javier Borrajo