On Sat, Jan 29, 2011 at 10:04 AM, Peter Bex
<address@hidden> wrote:
On Sat, Jan 29, 2011 at 11:57:27PM +0900, Daishi Kato wrote:
> After a quick look in the code, one suspect is that port-closed?
> can't check a closed port, but not really sure.
If that's the case, it's a bug in Chicken because http-client simply
used the definition from library.scm, and provides its own copy if we're
on an older Chicken that doesn't provide this procedure.
> Or, it doesn't raise an exception when it detects closed connection.
> I'll work more tomorrow and try to make a test case,
> but let me know if you already know this issue.
I have observed "weird' behaviours on closed connections before,
but always in error cases only, and I wasn't able to debug that,
so I'm not sure if that's the same issue you're reporting.
A test case would be welcome.
Cheers,
Peter
--
http://sjamaan.ath.cx
--
"The process of preparing programs for a digital computer
is especially attractive, not only because it can be economically
and scientifically rewarding, but also because it can be an aesthetic
experience much like composing poetry or music."
-- Donald Knuth