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: Tue, 06 Nov 2007 06:19:44 -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 felix):

 Replying to [comment:9 sjamaan]:
 > I see the problem with the ''http-server'', it simply does not output
 the proper connection mode.  When he originally implemented http-server
 and spiffy, Felix decided to put this functionality in spiffy, not in
 http-server.

 There is no particular reason, why http-server doesn't do the connection
 mode handling - it turned out to be simpler in spiffy (a design mistake,
 admittedly). `http:write-response-header` has no access to the current
 request, so it can't check protocol version or request headers for
 deciding on the proper handling. As I never used http-server directly
 (only as a low-level layer for spiffy), I simply decided to handle the
 connection mode in an upper layer. Putting it into http-server would have
 been the right thing to do.

-- 
Ticket URL: <http://trac.callcc.org/ticket/311#comment:11>
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]