To: Bjorn Stabell
Cc: [EMAIL PROTECTED]; Exoweb
Subject: Re: [Zope-dev] CoreSessionTracking 0.8 strangeness
Bjorn,
Is this entirely with cookies? Or are you using url-encoding anywhere?
Does your application make use of frames or multiple windows?
- C
Bjorn Stabell wrote:
>
> Chris,
>
Bjorn,
Is this entirely with cookies? Or are you using url-encoding anywhere?
Does your application make use of frames or multiple windows?
- C
Bjorn Stabell wrote:
>
> Chris,
>
> It is definately not what you expect, although it was a good guess :)
> Here's an example of what happens:
>
Bjorn
-Original Message-
From: Chris McDonough [mailto:[EMAIL PROTECTED]]
Sent: Friday, May 11, 2001 20:47
To: Bjorn Stabell
Cc: [EMAIL PROTECTED]; Exoweb
Subject: Re: [Zope-dev] CoreSessionTracking 0.8 strangeness
This is very odd, as cst depends on ZODB locking just like everything
els
This is very odd, as cst depends on ZODB locking just like everything
else in Zope, and uses the same transaction facilities and semantics.
Now this may *be* the problem... some other folks have explained a
problem where newly-created session data "disappears" if the
long-running request that cre
Hi,
We're developing a shopping cart using the CoreSessionTracking product
v0.8, but we've run into a strange problem; once in a while
getSessionData() will create a new session data object (the token value
remains the same), and us that for a while. Now we'll end up having two
different shoppi
