Re: Do DA's add a page to the app's cache ?
Re: Do DA's add a page to the app's cache ?
- Subject: Re: Do DA's add a page to the app's cache ?
- From: Chuck Hill <email@hidden>
- Date: Fri, 5 Sep 2008 11:11:53 -0700
On Sep 5, 2008, at 10:58 AM, William Hatch wrote:
On Sep 4, 2008, at 8:40 PM, Chuck Hill wrote:
On Sep 4, 2008, at 5:31 PM, William Hatch wrote:
I'm pretty sure that whenever you instance a new component using
pageWithName... it gets added to the page cache. I get around this
with the hackish method of adding this line in the components
constructor:
session().savePageInPermanentCache(this);
Does that not greatly increase memory usage?
It certainly could, but we only had a few instances and given how
much memory the app had allocated and what was available, (and being
unaware of your much better suggestion at the time) seemed to be an
ok trade off. Also, if the components you want to use are little
widegty type things (like summary views for a list inside a rep or
something like that) the other obvious thing would be to make them
stateless and not worry about it, if I'm correct in the belief that
stateless components are not kept in any page cache.
Well, it depends. :-) The top level "page" returned by an action
handler always gets in the page cache. If you use
pageWithName("StatelessComponentName"), then it effectively become
state-full and gets into the page cache.
Chuck
which is no where near as nice as what Wonder does, but does work.
I've never had memory problems.
Using this, you can instantiate the components in your DA, set
them up however, then get the result string from
generateResponse.... etc to ship it back to your js handler to do
whatever with, in most my cases it's InnerHTML type thing. Hope
that helps.
Bill
On Sep 4, 2008, at 7:48 PM, Owen McKerrow wrote:
Hi All,
We have an app that has some small hand made AJAX on it (not the
cool stuff from project wonder) and we're having an issue with
page cacheing on the Applications side.
I had set the AJAX action up as a call to a DA which I had though
did not add to/effect the sessions page cache. So either that
assumption is wrong or I haven't made a clean break between the
DA and the session after all.
Anyways heres the error we're getting...
"The application backtracking limit of 30 has been exceeded."
Any suggestions ? Is turning off caching an option ?
Owen McKerrow
WebMaster, emlab
Ph : +61 02 4221 5517
http://emlab.uow.edu.au
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - -
People who prefer typing to pointing then seem to prefer acronyms
to save typing :-)
-Denis Stanton, On people using Command Line Interfaces
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden