Home/ Questions/Q 8468681
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T16:00:11+00:00

I want to create a two-way stream between a Node.JS client and a Node.JS

  • 0

I want to create a two-way stream between a Node.JS client and a Node.JS server, via an HTTP connection. But it seems that the server’s request event is not called until the client calls req.end(). How can I establish a two-way communication? Do I need to use separate requests?

Clarification: My expectation was that it was possible for

  1. The client to send the request header,
  2. The server to send the response header, and
  3. The server and client to send bytes whenever they want.

Edit: OK, here is the summary of the options:

  • TCP sockets on a separate port: This is good if you don’t mind opening a separate port, and then modifying previous use of HTTP (request path and headers, and response headers) to use the stream instead. (I declined this option.)

  • Separate HTTP requests, ending the request every time you need to flush. Managing the state would be done in the application, because now an ended connection will no longer represent an ended session. (In the short term, I will use this option.)

  • Socket.IO (which is an implementation of WebSockets + reverse compatibility): This option is very appealing, but you need to add the Socket.IO layer to be in front of the HTTP layer. Socket.IO would pass through all HTTP requests, but WebSocket requests would be handled differently. (In the long term, I will use this option, but I will have to modify my front-end to permit this.)

    As I understand it, the Node.JS http library will not allow me to send a response header, unless the client has already completed (or at least substantially began) sending the request body. This I suppose is for good reason, so this third option can also be titled Add a layer in front of the http library.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If you are really looking for a 2-way communication system, HTTP is not really the correct protocol.. The whole idea is that it’s stateless and handled 1 request at a time. There’s exceptions to this rule, but those are really stretching what HTTP is supposed to do, and could be considered hacks.

    It sounds like you should be using something like Socket.IO

    • 0