On 7/21/05, Perrin Harkins <[EMAIL PROTECTED]> wrote: > > Could there be a problem that the output buffer of a previous request > > is not flushed completely (due to a broken connection perhaps), so > > that part of the output gets sent to the next client of the same > > process? > > I don't think so. > > This kind of thing is usually caused by a scoping bug, where something > is getting put into a global or a closure and unintentionally used on > consecutive requests. It could also be caused by multiple people > getting the same session ID, depending on what you use to generate them.
You are right, I turned on 'use strict' and found a scoping bug <blush> The upgrade was just a bad coincidence.. Sorry to have bothered you! Joost
