{"issue":{"milestone":null,"user":{"id":822369,"login":"tjanczuk","url":"https://api.github.com/users/tjanczuk","avatar_url":"https://secure.gravatar.com/avatar/53f70144dc9d7c76455fa91f858d4cec?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"53f70144dc9d7c76455fa91f858d4cec"},"created_at":"2011-12-15T20:56:39Z","title":"perf: detect length of chunked transfer encoding messages","labels":[{"name":"P1","url":"https://api.github.com/repos/tjanczuk/iisnode/labels/P1","color":"e10c02"},{"name":"perf","url":"https://api.github.com/repos/tjanczuk/iisnode/labels/perf","color":"0b02e1"}],"state":"closed","updated_at":"2011-12-17T00:09:32Z","id":2572415,"closed_at":"2011-12-17T00:09:31Z","pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"html_url":"https://github.com/tjanczuk/iisnode/issues/121","body":"Currently one named pipe connection per requests is used which allows us to rely on the heuristic that closing of that connection by the server implies the end of the response. Therefore we don't have to parse chunked responses. Two side effects of this design are that detecting the end of the response requires one extra ReadFile that causes one more context switch, and that we cannot reuse named pipe connections to the server for multiple requests (and creating new named pipe connections is expensive - about 7% of worker process time). \r\n\r\nThis is to implement a mechanism to detect the end of a chunked response by parsing chunked transfer encoding. \r\n\r\n","number":121,"url":"https://api.github.com/repos/tjanczuk/iisnode/issues/121","comments":0,"assignee":null},"action":"closed"}