Re: session backtracking cache
Re: session backtracking cache
- Subject: Re: session backtracking cache
- From: Chuck Hill <email@hidden>
- Date: Wed, 27 Aug 2003 14:32:49 -0700
I'd guess that checking the session out and in again is what resets this.
At least it seems like what I'd expect the session store to handle. If the
session is not already checked out, give this a try. If it is checked out,
hmmm, it ought not expire then, right?
Chuck
At 04:21 PM 27/08/2003 -0500, Jonathan Rochkind wrote:
>Yeah, I see what's up now, thanks.
>
>Okay, next question (which may not seem obviously related, but it is)...
>what resets the 'death count' for a session to time out? I know it's a
>'request to that session'.... but I guess what I'm really asking is, in the
>_absence_ of a request to that session, is there any way I can manually
>reset this value? I know I want to tell the WOSession with the ID X, "Hey,
>reset your clock, don't time out yet, consider this like a request even
>though it wasn't one!". Is there any way at all to do that?
>
>--Jonathan
>
>At 02:12 PM 8/27/2003 -0700, Chuck Hill wrote:
>>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
>
>
--
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.