Another argument for SFSB that I don't think has been mentioned yet in this
thread ...
Relative to HttpSessions, SFSBs provide a better separation of presentation
logic from application logic. If the application state is in SFSBs rather
than HttpSessions, it is easier to use multiple presentation layers with a
given application or parts of an application (e.g, a web interface, a Swing
interface).
Laurel
-----Original Message-----
From: Ian McCallion [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 31, 2001 3:36 AM
To: [EMAIL PROTECTED]
Subject: Re: EJB Session versus HttpSession
<stuff deleted>
I still hold to the view that keeping client state information in a SFSB is
the
right design point, unless your chosen app server's SFSB implementation does
not
scale sufficiently for your needs.
========================================
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".
