we're getting very close to making progress on this. see below
> -----Original Message-----
> From: Anne Thomas [SMTP:[EMAIL PROTECTED]]
> Sent: Sunday, May 16, 1999 7:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Real advantage of session bean wrappers?
>
> I like session bean wrappers because I really like the MVC pattern -- the
> client represents the view, the entity beans represent the model, and the
> session beans represent the controller.
[Frentress, James] we're in agreement that MVC is a great pattern
for overall distributed design. only the question of whether to use
"session-wrapper" remains.
> NOTE: I'm not recommending one session bean wrapper per entity bean.
> There's
> no value to session bean wrappers unless you are using the session bean as
> a
> concentrator.
[Frentress, James] agree
> In many applications the view uses multiple model instances.
[Frentress, James] agree
> If the client
> works directly with the entity beans, then the client has to get a
> reference
> for each entity bean instance.
[Frentress, James] disagree. you know that an entity (or many other
structures) can do this as well as a session.
> If you wrap the entities with a session bean,
> then the client only needs one reference.
[Frentress, James] if you replace the word "session" with the word
"entity" (or any number of structures), the statement still holds.
> The session bean manages all of
> the references to the entity instances.
[Frentress, James] see prior assertion.
> This approach definitely reduces
> resource requirements (one OUT reference versus many OUT references).
[Frentress, James] i'm tickled to see OUT used. i also use
NEAR-OUT, LAN-OUT, WAN-OUT, FAR-OUT to represent (same machine different vm,
same network, wide area network, farther than than - typically internet).
> You could implement the controller function using an entity bean (using a
> session ID as the primary key). This approach has some significant
> advantages -- the session data could be persistent, so you could easily
> recover a lost session.
[Frentress, James] if we were playing Stratego, you just captured
one of my (many ;) mid-level pieces -- this is an extremely powerful and
transparent fail-over and fault-tolerant mechanism to employ and i'm not
surprised you identified it.
> Anne
[Frentress, James] <snip>
===========================================================================
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".
