Timothy Gallagher wrote:
> I agree with Robb on this.
>
Thanks. :)
>
> ...The servlet should not contain any business logic. It should rely on
> lower level, or middle tier, objects to manipulate the data.
>
This having all been said, I should probably say that something I'm playing
around with is implementing a replacement for the typical RMI/CORBA middleware
using servlets.
That is, I'm looking into making a stateful OO RPC middleware that uses XML
over HTTP. In other words, instead of calling a method on an RMI proxy object,
you call a method on an HTTP proxy object, which connects to another servlet.
This may be a dead end, but it's an interesting project for a couple of
reasons: Anything under the sun can send a text string over http. (Java 1.02,
Smalltalk, etc.) HTTP goes through firewalls. HTTP is cheap, easy and
ubiquitous. The system would manage state transparently with cookies. This
means that a session could be started at one point in time, and stopped, and
picked up again from another location/point in time - all transparent to the
application and server programmers.
So, I'd still have a servlet client, but instead of it making a CORBA proxy
invocation:
server.getBusinessObject(param1);
I'd use an HTTP proxy object with an XML snippet as parameter, maybe like:
server.do("<method param=\"param1\">getBusinessObject</method>");
- Robb
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
