how can we cancel the ongoing stream process

[nkzawa]

how can we cancel the ongoing stream process

[peteruithoven]

On the server or the sending client?

[peteruithoven]

I have a server where I sometimes want to abort/disallow a incoming socket.io-stream event. But I noticed that calling .end() on the stream doesn't destroy it on the client that send the event.

  socket.io-parser decoded 2/user,["$stream-end","b1819055-c2fd-4b95-9405-3809383befca"] as {"type":2,"nsp":"/user","data":["$stream-end","b1819055-c2fd-4b95-9405-3809383befca"]} +0ms
  socket.io-stream:socket end: "b1819055-c2fd-4b95-9405-3809383befca" +0ms
  stream _end +0ms
  stream push  +0ms null

This means that the streams will stay and when the server restarts I get a [Error: Connection aborted] on the client.

On the client I could check the acknowledgment callback and when there is an error message, I could end() the stream. But I'd like to do this on the server, is there a proper way?

[nkzawa]

@mtalal16 Maybe you can just call stream#pause or stream#cork.

https://nodejs.org/api/stream.html#stream_readable_pause

[peteruithoven]

I'd like to warn for memory leaks. I think, on the broadcasting side, you need to manually call end() and destroy() to prevent the stream from hanging around.