[Seaside] Re: Connection Closed failure - should something handle this?

TimM tamackinnon at gmail.com
Fri Aug 20 07:15:36 UTC 2010

Kai-Uwe Pielka wrote:
> I'm running etumma.de with Pharo/Seaside on a debian server for several months now including Comet (for the shared slideshow you can use at etumma.de) and never got this error.

That's good to know - although having this, you may have jinxed 
yourself... and will find 3 tomorrow ;)

Still - it would seem that by signalling this - it could happen, and 
something should catch it?

Looking again, I see the following method in the stack:

WAListenerAdaptor>>waitForConnection: aSocket
	| socket stream |
	socket := aSocket waitForAcceptFor: 10.
	socket isNil ifTrue: [ ^ self ].
	stream := SocketStream on: socket.
	[ [ [ self process: stream ]
		ensure: [ stream close ] ]
			ifCurtailed: [ socket destroy ] ]
				forkAt: Processor userBackgroundPriority

Shouldn't that ifCurtailed: prevent this walkback?

More information about the seaside mailing list