[Seaside] handler reuse bug? [2.3]

[Avi Bryant]

On Sun, 20 Feb 2005 14:15:04 +0100, Michal <miso.list at auf.net> wrote:
 
> What I *think* is happening is: (i) a spider is generating a biggish
> load (there were about 3000 handlers when I VNCed into the server and
> netstat shows a couple of the usual suspects), (ii) seaside is reusing
> some expired handlers to cope with the incoming session requests,
> (iii) #collectExpiredHandlers first builds a collection of expired
> handlers and then unregisters them one by one, but by the time it
> sends #unregisterExpiredHandler:, the handler has been reused and its
> key has changed, hence the lookup in #unregisterExpiredHandler:
> triggers an error.

Hm, that's scary.  I can't think of anything it would be doing to
reuse handlers; it just creates new ones as needed.
 
Have you looked into this any further?

Avi