Chris McDonough wrote:
>
> But to make it happen you'd need ZPublisher to support a
> callback from ZServer when a connection was terminated.
> Since I know little about either, I'm not entirely confident
> I can be more specific.
yeah, well, even I was impressed how high above my head that flew
> Hmmm... does make for some pretty simple and very
> effective DOS attacks though
> :-S
>
> What would it take to fix it?
That depends on if you think it's broken... ;-)
But to make it happen you'd need ZPublisher to support a
callback from ZServer when a connection was terminated.
Since I kno
Chris Withers writes:
> Chris McDonough wrote:
> >
> > This is due to the relationship between ZServer and the publisher.
> > Sometimes it can be a bad thing... especially when there's an expensive
> > method that folks fire off that takes a long time.. nothing comes back to
> > their brows
Chris McDonough wrote:
>
> This is due to the relationship between ZServer and the publisher.
> Sometimes it can be a bad thing... especially when there's an expensive
> method that folks fire off that takes a long time.. nothing comes back to
> their browser, so they press stop and hit the page
o:[EMAIL PROTECTED]]
Sent: Friday, April 27, 2001 12:21 PM
To: Chris Withers; [EMAIL PROTECTED]
Subject: Re: [Zope-dev] CST 0.8 Updater Fixed...
> I stopped the above by wrapping the code as follows:
>
Cool!
> I wonder why it's necessary? Something to do with the weirdy mounted
i
> Unfortunately, it still sometimes hangs on certain instances :-S
> No error, no crash, just stops doing what it's doing (and Zope drops right
of
> 'top' IUKWIM)
>
> Playing with this, I noticed that Zope doesn't stop processing a request
if the
> browser goes away. Is that a bad thing? I would
> I stopped the above by wrapping the code as follows:
>
Cool!
> I wonder why it's necessary? Something to do with the weirdy mounted
internal
> session data container?
As Colonel Klink says so well, "I see nussing!"
___
Zope-Dev maillist - [EMA
Chris Withers wrote:
>
> Chris Withers wrote:
> >
> > It's running and working okay, but every so often, when running it, I get:
> >
> > 2001-04-27T09:15:23 PANIC(300) ZODB A storage error occurred in the last phase o
>
> I stopped the above by wrapping the code as follows:
Unfortunately, it st
Chris Withers wrote:
>
> It's running and working okay, but every so often, when running it, I get:
>
> 2001-04-27T09:15:23 PANIC(300) ZODB A storage error occurred in the last phase o
I stopped the above by wrapping the code as follows:
get_transaction().begin()
> path = self.getSess
