: Tony Wilson [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 06, 2001 10:55 AM
To: Orion-Interest
Subject: RE: ResultSet Caching
They can be used either as a replacement for en entity bean, or in most
cases, the method in which the Entity bean is saved.
If you don't need the overhead of EJB
: Tony Wilson [mailto:[EMAIL PROTECTED]]
Sent: Saturday, January 06, 2001 10:55 AM
To: Orion-Interest
Subject: RE: ResultSet Caching
They can be used either as a replacement for en entity bean, or in most
cases, the method in which the Entity bean is saved.
If you don't need the overhead of EJB
:31 PM
To: Orion-Interest
Subject: RE: ResultSet Caching
Right, I definitely wouldn't use an entity bean for list/search
functionality. Way too much
overhead. Stateless session beans is the way to go, but I don't think
throwing in large variable
sets into a session is a good solution either
PROTECTED]]
Sent: Friday, January 05, 2001 1:18 PM
To: Orion-Interest
Subject: RE: ResultSet Caching
What's the benefit of using those products over an entity bean then? How
does it differ?
Thanks.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tony
]
[mailto:[EMAIL PROTECTED]]On Behalf Of Conrad Chan
Sent: Friday, January 05, 2001 5:57 PM
To: Orion-Interest
Subject: RE: ResultSet Caching
I don't think entity bean can effectively solve your problem
since calling entity bean can potentially be remote calls.
Why not use session variables
