I would just like to clarify that I mean to use HttpSession to store your temporary
data rather than Session bean. A usual technique I have been using is to load a whole
bunch of kind-of static data and serialize it into Xml. Hence the XML data can be
stored in the HttpSession safely or even persistently since my XML data is just a
string. Of course a more sophisticated solution can also be built on top of this
generic architecture like cache time-out etc.
Hope this help
Conrad
-----Original Message-----
From: Neal Kaiser [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 05, 2001 4: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. Bloated sessions don't
perform well either.
Some app servers provide a caching solution, like Gemstone I believe, and I
was just wondering
if Orion had something similar..... I guess it makes most sense to just
re-issue the query for each
page. But if someone has any better ideas, I'm all ears! Thank you.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [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? Session variable is intended for
> temporary storage, like cache data.
>
> Conrad
>
> -----Original Message-----
> From: Neal Kaiser [mailto:[EMAIL 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 Wilson
> > Sent: Friday, January 05, 2001 3:50 PM
> > To: Orion-Interest
> > Subject: RE: ResultSet Caching
> >
> >
> > There are products that act as middlemen between you and the
> > Database. They
> > also offer database object abstraction (so you can have an object
> > representing table data. You define field -> property mappings, and the
> > product handles the transfer of data.)
> >
> > These products usually have built-in caching.
> >
> > Two products are
> > TopLink (expensive, but nice) http://www.objectpeople.com
> > VBSF (pretty inexpensive, and still nice) http://www.objectmatter.com
> >
> > -----Original Message-----
> > From: Neal Kaiser [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, January 05, 2001 10:49 AM
> > To: Orion-Interest
> > Subject: ResultSet Caching
> >
> > Does Orion have any built in caching functionality? Let's
> > say I have a
> > database query which returns 1,000 records and the user will
> > page thru 100
> > at a time. Instead of re-issuing the query each time (each
> > page), is there
> > some sort of cache object? How do you guys typically handle
> > this?
> >
> > Thanks, Neal
> >
> >
>
>
