chicken-janitors
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Chicken-janitors] Re: [Chicken-bugs] #311: http-server and http-client


From: Chicken Scheme
Subject: [Chicken-janitors] Re: [Chicken-bugs] #311: http-server and http-client doesn't handle keep-alive very well.
Date: Mon, 29 Oct 2007 22:02:28 -0000

#311: http-server and http-client doesn't handle keep-alive very well.
-------------------+--------------------------------------------------------
Reporter:  daishi  |        Owner:  sjamaan   
    Type:  defect  |       Status:  assigned  
Priority:  minor   |    Component:  extensions
 Version:  2.6     |   Resolution:            
Keywords:          |  
-------------------+--------------------------------------------------------
Comment (by daishi):

 Hi,

 Let us work with the second issue at first.

 I worked several hours, but I can't reproduce a "Borken pipe" error within
 a localhost.
 Maybe, it could be a NAT issue.
 My understanding is that the problem is a "Broken pipe" error when reading
 or writing from/to a port.

 At the point of filing this ticket, I didn't have any solution. As of now,
 I came up with an idea.
 The point is catching a "Broken pipe" error, and try again. Currently,
 http-client only cares about (exn i/o net). If the "Broken pipe" error is
 (exn i/o), we could simply use (exn i/o) instead of (exn i/o net).

 I'm afraid the "Broken pipe" error is not (exn i/o).
 What could we do in that case?

-- 
Ticket URL: <http://trac.callcc.org/ticket/311#comment:6>
Chicken Scheme <http://www.call-with-current-continuation.org/>
The CHICKEN Scheme-to-C compiler

reply via email to

[Prev in Thread] Current Thread [Next in Thread]