Thread: [Jaxor-devel] Cache

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Is the cache from a query only available to the same Jaxor context?  

Carl

Yes, caching is done on a per context basis. Did you
have a particular use case where you want to share a
cache? The cache interface is really simple, just a
few methods. It wouldn't be hard to implement a
different one that could be shared across contexts. It
all depends on the use case. 

Mike

--- Carl Fyffe <car...@gm...> wrote:

> Is the cache from a query only available to the same
> Jaxor context?  
> 
> Carl
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic
> Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1
> today.
>
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> Jaxor-devel mailing list
> Jax...@li...
>
https://lists.sourceforge.net/lists/listinfo/jaxor-devel
> 

__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail 

The use case is a search that returns more hits than is viewable at
one time.  I have done this in two ways (in the past).  The first way
I tried was stateless, every time the user asks for the next page, the
system goes back to the database.  This proved to be slower than
loading up all of the results into the HttpSession and then going back
to the Session anytime we needed to grab the next page.  This may have
had a LOT to do with the performance of the database, we had a crap
ERD and we were forced to access the tables via stored procedures.

So, let me turn this around.  Did I have the right idea about keeping
the query stateless?

On Sat, 11 Sep 2004 19:35:26 -0700 (PDT), Michael Rettig
<mik...@ya...> wrote:
> Yes, caching is done on a per context basis. Did you
> have a particular use case where you want to share a
> cache? The cache interface is really simple, just a
> few methods. It wouldn't be hard to implement a
> different one that could be shared across contexts. It
> all depends on the use case.
> 
> Mike
> 
> 
> 
> 
> --- Carl Fyffe <car...@gm...> wrote:
> 
> > Is the cache from a query only available to the same
> > Jaxor context?
> >
> > Carl
> >
> >
> >
> -------------------------------------------------------
> > This SF.Net email is sponsored by BEA Weblogic
> > Workshop
> > FREE Java Enterprise J2EE developer tools!
> > Get your free copy of BEA WebLogic Workshop 8.1
> > today.
> >
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> > _______________________________________________
> > Jaxor-devel mailing list
> > Jax...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/jaxor-devel
> >
> 
> 
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
>

I typically cache the results in the session, but
provide enough information in the request to refetch
the results if I lose the session. If you are paging
through query results, I would probably just drop it
in to the session. The risk is always that the user
loses the session and requests the next page, but
you've lost the query results. 

What are you putting in the session? The JaxorContext?
Or just a list that is returned from a query?

--- Carl Fyffe <car...@gm...> wrote:

> The use case is a search that returns more hits than
> is viewable at
> one time.  I have done this in two ways (in the
> past).  The first way
> I tried was stateless, every time the user asks for
> the next page, the
> system goes back to the database.  This proved to be
> slower than
> loading up all of the results into the HttpSession
> and then going back
> to the Session anytime we needed to grab the next
> page.  This may have
> had a LOT to do with the performance of the
> database, we had a crap
> ERD and we were forced to access the tables via
> stored procedures.
> 
> So, let me turn this around.  Did I have the right
> idea about keeping
> the query stateless?
> 
> 
> On Sat, 11 Sep 2004 19:35:26 -0700 (PDT), Michael
> Rettig
> <mik...@ya...> wrote:
> > Yes, caching is done on a per context basis. Did
> you
> > have a particular use case where you want to share
> a
> > cache? The cache interface is really simple, just
> a
> > few methods. It wouldn't be hard to implement a
> > different one that could be shared across
> contexts. It
> > all depends on the use case.
> > 
> > Mike
> > 
> > 
> > 
> > 
> > --- Carl Fyffe <car...@gm...> wrote:
> > 
> > > Is the cache from a query only available to the
> same
> > > Jaxor context?
> > >
> > > Carl
> > >
> > >
> > >
> >
>
-------------------------------------------------------
> > > This SF.Net email is sponsored by BEA Weblogic
> > > Workshop
> > > FREE Java Enterprise J2EE developer tools!
> > > Get your free copy of BEA WebLogic Workshop 8.1
> > > today.
> > >
> >
>
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> > > _______________________________________________
> > > Jaxor-devel mailing list
> > > Jax...@li...
> > >
> >
>
https://lists.sourceforge.net/lists/listinfo/jaxor-devel
> > >
> > 
> > 
> > __________________________________
> > Do you Yahoo!?
> > New and Improved Yahoo! Mail - 100MB free storage!
> > http://promotions.yahoo.com/new_mail
> >
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE.
> Be one of 170
> Project Admins to receive an Apple iPod Mini FREE
> for your judgement on
> who ports your project to Linux PPC the best.
> Sponsored by IBM.
> Deadline: Sept. 24. Go here:
> http://sf.net/ppc_contest.php
> _______________________________________________
> Jaxor-devel mailing list
> Jax...@li...
>
https://lists.sourceforge.net/lists/listinfo/jaxor-devel
> 

__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail 

Just the list that is returned from a query.  Is there a better way?

On Wed, 22 Sep 2004 21:49:40 -0700 (PDT), Michael Rettig
<mik...@ya...> wrote:
> I typically cache the results in the session, but
> provide enough information in the request to refetch
> the results if I lose the session. If you are paging
> through query results, I would probably just drop it
> in to the session. The risk is always that the user
> loses the session and requests the next page, but
> you've lost the query results.
> 
> What are you putting in the session? The JaxorContext?
> Or just a list that is returned from a query?
> 
> 
> --- Carl Fyffe <car...@gm...> wrote:
> 
> > The use case is a search that returns more hits than
> 
> 
> > is viewable at
> > one time.  I have done this in two ways (in the
> > past).  The first way
> > I tried was stateless, every time the user asks for
> > the next page, the
> > system goes back to the database.  This proved to be
> > slower than
> > loading up all of the results into the HttpSession
> > and then going back
> > to the Session anytime we needed to grab the next
> > page.  This may have
> > had a LOT to do with the performance of the
> > database, we had a crap
> > ERD and we were forced to access the tables via
> > stored procedures.
> >
> > So, let me turn this around.  Did I have the right
> > idea about keeping
> > the query stateless?
> >
> >
> > On Sat, 11 Sep 2004 19:35:26 -0700 (PDT), Michael
> > Rettig
> > <mik...@ya...> wrote:
> > > Yes, caching is done on a per context basis. Did
> > you
> > > have a particular use case where you want to share
> > a
> > > cache? The cache interface is really simple, just
> > a
> > > few methods. It wouldn't be hard to implement a
> > > different one that could be shared across
> > contexts. It
> > > all depends on the use case.
> > >
> > > Mike
> > >
> > >
> > >
> > >
> > > --- Carl Fyffe <car...@gm...> wrote:
> > >
> > > > Is the cache from a query only available to the
> > same
> > > > Jaxor context?
> > > >
> > > > Carl
> > > >
> > > >
> > > >
> > >
> >
> -------------------------------------------------------
> > > > This SF.Net email is sponsored by BEA Weblogic
> > > > Workshop
> > > > FREE Java Enterprise J2EE developer tools!
> > > > Get your free copy of BEA WebLogic Workshop 8.1
> > > > today.
> > > >
> > >
> >
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> > > > _______________________________________________
> > > > Jaxor-devel mailing list
> > > > Jax...@li...
> > > >
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/jaxor-devel
> > > >
> > >
> > >
> > > __________________________________
> > > Do you Yahoo!?
> > > New and Improved Yahoo! Mail - 100MB free storage!
> > > http://promotions.yahoo.com/new_mail
> > >
> >
> >
> >
> -------------------------------------------------------
> > This SF.Net email is sponsored by: YOU BE THE JUDGE.
> > Be one of 170
> > Project Admins to receive an Apple iPod Mini FREE
> > for your judgement on
> > who ports your project to Linux PPC the best.
> > Sponsored by IBM.
> > Deadline: Sept. 24. Go here:
> > http://sf.net/ppc_contest.php
> > _______________________________________________
> > Jaxor-devel mailing list
> > Jax...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/jaxor-devel
> >
> 
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - Send 10MB messages!
> 
> 
> http://promotions.yahoo.com/new_mail
>