I realize the benefits of separating business logic from the presentation
between servlets and jsp. However I wondering if anyone actually takes it
one step further and actually goes to a remote object layer (RMI or CORBA).
There obvious advantages to that are that any other application based on any
technology (client server, host-based or web) can plug right in using these
common objects. BUT, what I'm curious about it the overhead of worrying
about such things given that there is an obvious trend of less development
toward client/server and MUCH more web. (The other overhead would be in
actual execution time as well). While I like the model, is it really worth
it?
Also, as far as separation goes, I'm currently using a process where i've
got:
JSP->servlet->SQL helper classses specific to the servlet->generic SQL
helper classes to do the grunt work.
I'm always looking for better ways and would like any comment as to what
others are doing.
I've been an ASP developer for 3 years and have jumped in to this JSP/Sevlet
stuff a month ago. I absolutely love this compared to ASP. Its 100 times
cleaner and you can easily get to much more powerful api's simpler and
faster. To any of the people designing the JSP/Servlet specs: keep up the
excellent work - i'd be surprised if anyone does web development using
anything else in a year or so.
Steve
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
