As far as I know, only the cookie or id of the HTTPSession go between the
client and the server. Most vendors implement the data stored in the
HTTPSession on the server side. It would not be practical to send the data
back and fourth since, there would be no place to store it on the client's
side (please correct me if I am wrong here). Cookie can only be so large,
and some of the data can be of binary nature.
-AP_
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Ian McCallion
Sent: Monday, July 30, 2001 7:29 AM
To: [EMAIL PROTECTED]
Subject: Re: EJB Session versus HttpSession
John Bateman wrote:
>
> Hi
>
> I'm assuming when you say that information passed / stored in the
> HttpSession will be passed up the wire you mean sent back and forth from
the
> App server.
HTTPSession data goes up and down the wire between the client and the web
server. It's a neat trick, because it absolves the web server from state
management, but it should be used in moderation.
> I, maybe due to my limited experience, can't see how using references to a
> session bean on the client side can reduce network I/O in lieu of just
> stuffing (temp)variables into the HTTPSession and processing them when
> ready. If I process the 7 form 'wizard', with validatred data from the
> forms, and then send it along to my session bean, doesn't this now create
> only one big bulk update on the business side instead of 7 little updates?
> (Refer MVC, Model 2 / Request dispatcher Pattern and the Struts Project at
> Apache.org)
It very much depends on the application. If it's an internal application
where
the chance that the user will get fed up and decide not to continue with the
form-filling is minimal, then you may be right that the best design is a
stateless session bean to do the seven little updates.
But if it's an internet application, probably 50% of the people who start
the
process of filling in the 7 forms will never complete them, so it would be
better to remember the state in a Stateful Session Bean and only update the
big
database at the end, IF the user finishes.
Ian
========================================
Ian McCallion
Alexis Systems Limited
Romsey, UK
Tel: +44 1794 514883
Fax: +44 1794 501692
========================================
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
