Randy,
Thanks for your long and very describing post. However, most
respectfully, most of it described ideas and prectices used by us for
quite some time now, only that we do not use the term "application
layer". At Suns .Com practice, we call it the "presentation layer" which
serves the "Client layer", i.e. the browser in this case. So I guess
that there are parts of the community who regards that layer having a
different name. I was curious if you had some other ideas, hence my
question.
However, let me comment on this passage:
Randy Stafford wrote:
> Since the servlets and JSP beans are so customized to support the use cases
> going on, and so "close to the glass", they form the natural place to store
> conversational state. In their context they know the selections of data the
> user has made, the edits s/he has made, and the actions s/he is trying to
> take - therefore they have the most context with which to invoke services,
> retry failed invocations, give error messages to the user and redirect the
> user, etc.
I most certainly agree with the second sentence. But to me that does not
mean that it is also the natural place for keeping state. If the state
to keep is defined by the service used, meaning that everybody using it
must keep the same state, IMHO the stateful bean might as well keep it.
If the client/application layer, using your terminology, has its own
state (selections in boxes etc) to keep, the application layer is a good
place for it. To me it is all a matter of responsibility.
I'm off for a one week vacation so I will not be able to participate in
the discussion for that time. Thanks all for a very stimulating thread
so far.
Regards,
/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".
