Scalability and fail-over-ability of HttpSessions vs. SSB/SLSB is dependent
on vendor implementation. Some vendors are better at the former, others are
better at the latter. Kang wrote an article about this on javaworld.com:
http://www.javaworld.com/jw-02-2001/jw-0223-extremescale.html
But of course, this article is dated, and recent vendor releases have made
the picture more complex. For example, WL 6.0/6.1 now supports failover
SFSB, etc...
Gene Chuang
Kiko.com
-----Original Message-----
From: Laurel Neustadter [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 30, 2001 8:02 AM
To: [EMAIL PROTECTED]
Subject: Re: EJB Session versus HttpSession
According to a Gemstone paper on theserverside.com, stateful session beans
aren't scalable (due to the activation/passivation expense, creation
expense). According to that article, if the number of users will ever grow
to beyond a few thousand, stateless session beans should be used. Of course,
the exact numbers must be server-dependent. But it seems scalability is
another consideration when choosing between stateful/stateless session
beans.
The URL for the article is
http://theserverside.com/resources/article.jsp?l=ICommerce-Design-Strategies
#stateful.
Laurel
-----Original Message-----
From: Ian McCallion [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 30, 2001 8:51 AM
To: [EMAIL PROTECTED]
Subject: Re: EJB Session versus HttpSession
Piyush Nigam wrote:
>
> Hi,
> I have a scenario where seven forms are submitted to complete a
> transaction. My options are to :
> 1) maintain all the values from each form in the HttpSeession and on the
> final submission call a stateless session bean to manage my transaction.
> This ensures fewer remote calls
> 2) Reach values submitted by each form to a stateless session bean and
keep
> passing its handle in the HttpSession. This reduces remote calls but
places
> the session management responsibility on a less efficient framework.
>
> What do you think is the better choice?
(1) If you use HTTPSession for the data it will travel up and down the wire
each
time. This could create a possible security problem and could create a
possibly
worse performance problem than using a Session Bean.
(2) If you use a Stateless Session Bean you'll need to save the partially
complete (and maybe never-to-be-completed) data on a database.
(3) So I'd say use a Stateful Session Bean.
cheers... 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".
===========================================================================
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".
