<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>Ah oki, thanks. I'll mess with it when I get home.. probably have another question or two.<br><br>RS<br><br>> Date: Tue, 14 Jun 2011 18:10:45 +0200<br>> Subject: Re: [Seaside] From July/August 2010 (Thread: WAListener error)<br>> From: philippe.marschall@gmail.com<br>> To: seaside@lists.squeakfoundation.org<br>> <br>> 2011/6/14 Robert Sirois <watchlala@hotmail.com>:<br>> > Connection Closed<br>> > http://lists.squeakfoundation.org/pipermail/seaside/2010-August/024262.html<br>> > WAListener Error<br>> > http://lists.squeakfoundation.org/pipermail/seaside/2010-July/023793.html<br>> > I still have this problem with WAListenerAdaptor. Anyone else? And if so,<br>> > Nick Ager proposed this workaround<br>> > http://lists.squeakfoundation.org/pipermail/seaside/2010-August/024266.html<br>> > Is that valid?<br>> <br>> The bug or the fix? The bug, probably yes, various network<br>> intermediaries may close an HTTP request they don't like for whatever<br>> reason (eg. they believe it's hanging). Or the TCP connection may fail<br>> "in the middle" for what ever reason else (the device ran out of<br>> power, crashed, …).<br>> <br>> The fix, it would probably be better to handle ConnectionClosed and<br>> various other errors the same way Kom does it.<br>> <br>> Cheers<br>> Philippe<br>> _______________________________________________<br>> seaside mailing list<br>> seaside@lists.squeakfoundation.org<br>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside<br> </body>
</html>