propagating end events to server

[soldair]

fixes. Leaks all client ended read streams.

readable streams passed from server to client like level-live-stream that never end on the server cannot be ended from multilevel client. the server never gets the end event though they are supported by mdm and the client ends them.

the fix is when a tmp-stream is "replaced" with the mdm stream bind end on the tmp stream to trigger end on the mdm stream. for write stream support also close should be bubbled.

this example results in the whole database being streamed to the client. you can see it if you bind "data" on the mdm stream to console log or just look at your server's network traffic graph.

db.createReadStream().once('data',function(){ this.end(); })

the expected behavior is that the server side of the stream gets the end event that mdm passes and stops streaming the whole database.

[soldair]

this bug is super duper bad in my case because i have a db server process that many api server processes connect to with a single long lived connection. Any api client request that results in a live stream leaks the hook in the db server process and maxes out process rather quickly.

[juliangruber]

i'm looking at this now...progress! :D