You've caught it right. I neant some abstracted functionality
common for all such business objects (unique transaction ID
travelling with requests/responses and possibly something else).
> -----Original Message-----
> From: A mailing list for discussion about Sun Microsystem's Java Servlet
> API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Spike
> Washburn
> Sent: Tuesday, March 21, 2000 3:50 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Modelling use cases with JSPs/Servlets
>
> I don't quite I follow what you'd like to see in this "HttpChain"
interface
> that you feel would be an important improvement for servlets. Can you give
> a little example of what you'd like it to do for you?
>
> If you're looking for someway to maintain the state of a business object
or
> transactions for the client between HTTP requests, why wouldn't putting a
> business object into the user's session be acceptable? On each
> request from
> the client, the servlet would then translate the user's HTTP
> request into an
> action on the business object in the user's session.
___________________________________________________________________________
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
