10

So, I want to use node.js and http request pipelining, but I want to use HTTP only as a transport, nothing else. I am interested in exploiting the request pipelining feature. However, one problem that I am running into is that till a send a response to a previous request, the next requests's callback isn't fired by node. I want a way to be able to do this. I shall be handling the ordering of results in the application. Is there a way to do this?

The HTTP RFC mentions that the responses should be in order, but I don't see any reason for node.js to not call the next callback till the 1st one is responded to. The application can in theory send the response to the 2nd query as a response to the 1st one (as long as there is some way for the recipient to know that it is a response to the 2nd one).

generalhenry
  • 17,227
  • 4
  • 48
  • 63
dhruvbird
  • 6,061
  • 6
  • 34
  • 39
  • Okay, there doesn't seem to be any way that I can see. Will have to write an HTTP parser and server component. – dhruvbird Mar 27 '11 at 05:25
  • 2
    Did you ask on the Node.js IRC channel? (on freenode) Theres plenty of very good help there – David Apr 11 '11 at 08:25

1 Answers1

6

The HTTP client in NodeJS does not support pipelining. (Slightly old post from Ryan, but I'm fairly sure it still holds.)

mjs
  • 63,493
  • 27
  • 91
  • 122
  • Well, if the client does not support pipelining, there are very slim chances of it supporting what I wanted!! Thanks!! :-) – dhruvbird Apr 26 '11 at 04:37