Re: session backtracking cache
Re: session backtracking cache
- Subject: Re: session backtracking cache
- From: Chuck Hill <email@hidden>
- Date: Wed, 27 Aug 2003 14:12:32 -0700
Is there any way for you to tell this at the session level? I have this in
one of my apps where I want to keep the cache size down:
public void savePage(WOComponent aPage) {
if (shouldCachePage(aPage))
{
super.savePage(aPage);
}
}
shouldCachePage() looks at a few things to determine if the page should be
cached. One of those is an instanceof test. I make pages that don't
contain component actions implement an interface, say UnActionable. For
some other pages, I cast aPage and ask it directly if it needs to be cached
or not.
Perhaps one of those will inspire you.
Chuck
At 04:02 PM 27/08/2003 -0500, Jonathan Rochkind wrote:
>If you have a direct action, which returns a WOComponent, but that
>WOComponent has no component actions whatsoever, it only includes direct
>actions itself.... then there's really no reason for that component to be
>stored in the session's page cache. But it appears it is anyway.
>
>Is there any way at all to prevent this?
>
>[In case you're wondering, there are several big problems with the
>upload-with-progress-bar code I posted about yesterday. Sigh. Man, if I
>ever do get this working, it'll be astounding.]
>_______________________________________________
>webobjects-dev mailing list | email@hidden
>Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
>Do not post admin requests to the list. They will be ignored.
>
--
Chuck Hill email@hidden
Global Village Consulting Inc. http://www.global-village.net
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.