Anjo,
thanks, but with new knowledge comes confusion...
I only cared about direct actions, because I thought component actions
were magically taken care of. I assumed that as soon as "Refuse new
sessions" was set in JavaMonitor for instance X, component requests
that did not have a session were passed on to another instance without
ever getting to instance X. Back in the days before I had session
cookies and a lot of direct actions, that was the way it worked for
me. But now I am seeing some new sessions being created by component
actions in instance X, possibly because of session cookies from a
different instance.
Am I wrong in my assumptions about component requests? Am I going to
have to check every single request, both direct action and component?
That doesn't sound right.
In fact, surely the best result would be "magically" make direct
actions work the way I thought component actions worked, so that
clicking "Refuse new sessions" just worked...
Regards
Thomas
On 08/02/2008, at 8:23 AM, Anjo Krank wrote:
>
> Am 07.02.2008 um 22:17 schrieb Thomas:
>
>> But I was assuming that was the case already-- the documentation
>> for existingSession() says that is what it does. Am I missing
>> something? Was that broken? The fact that I am still getting
>> sessions sometimes when calling this suggests that something is
>> broken.
>
> existingSession() is a method on WODirectAction. There was no
> corresponding method on WOContext. And hasSession() returned false
> in the case I stated.
>
> Cheers, Anjo
>
This archive was generated by hypermail 2.0.0 : Thu Feb 07 2008 - 16:56:25 EST