Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-26 Thread Joachim Werner
dtml-let data=SESSION.getSessionData() manage=REQUEST.get('manage_content') or data.get('manage_content') dtml-unless manage dtml-call data.set('manage_content','NO') /dtml-unless dtml-in data.keys() dtml-let si=sequence-item dtml-call REQUEST.set(si, data[si])

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-25 Thread Chris McDonough
To further try to track this problem down, I've developed a burger, fries, coke application in honor of this thread. So far, I've eaten 84 burgers, 31 cokes, and 42 fries. I can't seem to break this thing, and I'm not hungry anymore. :-( I just wanted to throw this out there. I'm certain

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-25 Thread Chris McDonough
Matt Hamilton wrote: Just to add myself to the list, I too am having problems with CoreSessionTracking :( I am trying to find a test case for the problem, but I really can't replicate it. It first I thought it was a cookie issue, but I am now noting down the session id generated and it

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-25 Thread Matt Hamilton
On Fri, 25 May 2001, Chris McDonough wrote: Bummer. How long is the session data container timeout set for? Are you sure you're just not exceeding the timeout? The session timeout is 120 minutes. I am using an external SessionDataComainter stored in the normal undo-able ZODB (I'm not

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-25 Thread Chris McDonough
Matt Hamilton wrote: Looking into it further I don't think it is a CST fault :) I think I have fixed the problem. It was me not setting _p_changed on an object with a dict after adding items to the dict. Hence the session wasn't being lost, just the conents of the cart itself were not very

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-25 Thread Chris McDonough
Chris McDonough wrote: If the answer is 2, everything's not so fine. I'll likely need to change the CST code to unwrap acquisition-wrapped objects before storing them, just to head potential problems off at the pass. I just did a preliminary test, and it appears that it *is* storing

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-25 Thread Chris Withers
Chris McDonough wrote: To further try to track this problem down, I've developed a burger, fries, coke application in honor of this thread. So far, I've eaten 84 burgers, 31 cokes, and 42 fries. I can't seem to break this thing, and I'm not hungry anymore. :-( Sorry, but I had to :-)

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-25 Thread Chris Withers
Chris McDonough wrote: Note that I just changed CST to unwrap aq-wrapped objects just in case, I always wondered why Squishdot did this, now I know :-) cheers, Chris ___ Zope-Dev maillist - [EMAIL PROTECTED]

RE: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-25 Thread Bjorn Stabell
Chris McDonough: [...] weeping (although grateful for the exchange), I'm sorry Chris. We didn't give you a very good debugging chase. I know how frustrating bug reports like Help! It doesn't work is, but I guess it's very hard to troubleshoot bugs in frameworks since there's so much

Brought to you live: The Bug (RE: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8))

2001-05-25 Thread Bjorn Stabell
By the way, Chris, you can see the bug in action at our site by going to: http://www.beijingsammies.com:7380/sammies/ The website has not been launched yet, so be careful guys. Also, don't try ordering, unless you're in Chaoyang district, Beijing, China. :) The site may be slow since

RE: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-25 Thread Bjorn Stabell
, -- Bjorn -Original Message- From: Matt Hamilton [mailto:[EMAIL PROTECTED]] Posted At: Saturday, May 26, 2001 00:37 Posted To: Zope Developer Conversation: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8) Subject: RE: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8) On Fri, 25 May

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-25 Thread Chris McDonough
Hi Joachim, I'm confused as to the utility of this bit of code. You loop over the items in the REQUEST.form dict, putting them all into session storage except for 'file'. Then you loop over all the items in the session data object, putting them into the REQUEST.other dict. Why the first step?

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-24 Thread Joachim Werner
What we experience with CoreSessionTracking: We have a manage mode in the Kontentor CMS hacky thing (no, it is NOT a product yet ;-)). It works well for some time (i.e. if I click on it, the system switches to manage mode and stays in manage mode until I click again), but from time to time it is

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-24 Thread Chris McDonough
These it appears CST is unstable reports are helpful to an extent (from Bjorn, Joachim, and Howard), as it lets me know that something needs to be done to CST. However, a much more helpful report would be one which provides a repeatable test case which invariably reproduces the problem instead

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-24 Thread Matt Hamilton
On Thu, 24 May 2001, Chris McDonough wrote: These it appears CST is unstable reports are helpful to an extent (from Bjorn, Joachim, and Howard), as it lets me know that something needs to be done to CST. However, a much more helpful report would be one which provides a repeatable test case

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-24 Thread Joachim Werner
However, a much more helpful report would be one which provides a repeatable test case which invariably reproduces the problem instead of one which states the symptoms and effects of the problem. I know, but that's why the errors are called random: They are not easy to replicate ...

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-24 Thread Chris McDonough
Joachim Werner wrote: However, a much more helpful report would be one which provides a repeatable test case which invariably reproduces the problem instead of one which states the symptoms and effects of the problem. I know, but that's why the errors are called random: They are not

Re: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-24 Thread Chris McDonough
Chris McDonough wrote: I just wrote a test case that emulates many visitors firing off sessions and making changes to shared data objects simultaneously. It even emulates aborted connections. Unfortunately, I see nothing out of the ordinary. :-( This is very frustrating. Maybe the

[Zope-dev] CoreSessionTracking 0.8

2001-05-23 Thread Howard Zhang
Hi The problem about CoreSessionTracking we describe before we can repeat again now. The step is: ( 1 ) User adds Burger to shopping cart ( 2 ) User adds coke to shopping cart and click link to add coke again before request finished ( 3 ) The Burger is

Re: [Zope-dev] CoreSessionTracking 0.8

2001-05-23 Thread Chris McDonough
I remember this problem, but I haven't been able to reproduce it. But maybe it's because I'm not understanding the steps to reproduce it. The sentence user adds coke to shopping cart and click link to add coke again before request finished is hard to understand. Can you explain? Are you using

Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-23 Thread Bjorn Stabell
Zhang Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; Exoweb Subject: Re: [Zope-dev] CoreSessionTracking 0.8 I remember this problem, but I haven't been able to reproduce it. But maybe it's because I'm not understanding the steps to reproduce it. The sentence user adds coke to shopping cart and click

RE: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8)

2001-05-23 Thread Albert Langer
: Randomness (RE: [Zope-dev] CoreSessionTracking 0.8) Allright, let me try again. I wish I had a small piece of code to give you so you can reproduce it, but right now you'd have to get our entire CMF-based website. The bug basically manifests itself in that there are two versions of the variable we

Re: [Zope-dev] CoreSessionTracking 0.8

2001-05-23 Thread Bill Anderson
On 23 May 2001 19:00:41 +0800, Howard Zhang wrote: Hi The problem about CoreSessionTracking we describe before we can repeat again now. The step is: ( 1 ) User adds Burger to shopping cart ( 2 ) User adds coke to shopping cart and click link to add coke again

RE: [Zope-dev] CoreSessionTracking 0.8 strangeness

2001-05-13 Thread Bjorn Stabell
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, It is definately

RE: [Zope-dev] CoreSessionTracking 0.8 strangeness

2001-05-12 Thread Bjorn Stabell
- 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 else in Zope, and uses the same

Re: [Zope-dev] CoreSessionTracking 0.8 strangeness

2001-05-12 Thread Chris McDonough
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: 1.

[Zope-dev] CoreSessionTracking 0.8 strangeness

2001-05-11 Thread Bjorn Stabell
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

Re: [Zope-dev] CoreSessionTracking 0.8 strangeness

2001-05-11 Thread Chris McDonough
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