[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Chicken-janitors] #1579: spiffy does not flush output port
From: |
Chicken Trac |
Subject: |
[Chicken-janitors] #1579: spiffy does not flush output port |
Date: |
Thu, 17 Jan 2019 18:28:54 -0000 |
#1579: spiffy does not flush output port
------------------------+--------------------------------
Reporter: zbigniew | Owner:
Type: defect | Status: new
Priority: major | Milestone: someday
Component: extensions | Version: 5.0.0
Keywords: spiffy | Estimated difficulty: easy
------------------------+--------------------------------
Port slot 8 (closed?) changed from a bool to a fixnum in Chicken 5, which
made the existing port closed test in handle-incoming-request always
succeed, so output was never flushed.
This can lead to hangs when output size is less than tcp-buffer-size. This
behavior was observed in chickadee when output size < 1024, including on
simple responses like 302 redirects.
Fix is to use the official accessor instead, which seems to work fine. I'm
not sure if this was a legacy thing, but other procedures in the spiffy
code use port-closed?.
Patch is attached.
--
Ticket URL: <https://bugs.call-cc.org/ticket/1579>
CHICKEN Scheme <https://www.call-cc.org/>
CHICKEN Scheme is a compiler for the Scheme programming language.
- [Chicken-janitors] #1579: spiffy does not flush output port,
Chicken Trac <=