Randy Stafford wrote:
>
> Marcus Ahnve wrote:
>
> > > It
> > > then becomes a design choice where to store it. Storing it in stateful
> > > session beans may limit scalability, as you suspect. What is wrong with
> > > storing it in HttpSession state?
> >
> > Because then every client has to store their own session instead of just
> > being responsible of displaying things to the users.
> >
> [Randy Stafford] It is the responsibility of the presentation layer
> to display things to users. The application layer, implemented with
> servlets or JSP beans, for example, is responsible for mediating between the
> presentation layer and the services layer, and is a logical and likely place
> to store conversational state.
I regard the servlet/jsp as being part of the presentation layer, and
therefor not the natural place for storing sessions. However I'm curious
about what you are calling the application layer, I guess that it's
mentioned in your "iCommerce, design issues and solutions" paper which I
unfortunately have not yet had the time to read. But easter is coming up
with a lot of sparetime so I might just have changed my mind come
monday. Otherwise I'll be back with a lot of new arguments ;-).
/Marcus
Marcus Ahnve
Sun Java Center
Sweden
===========================================================================
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".
