David Halls
David Halls
Just upgraded to 0.12.2, the `all_targets` method is still there but deprecated. I'm not using delegations so is it okay to carry on using it?
Unless there's some feature which needs ES6 I don't see the point of rewriting code which works. As long as it's readable I think it's fine.
With a Streams2 interface, would we get help with back-pressure?
That makes sense but I got confused with this in the README: > This method always returns true so back pressure isn't handled.
@3rd-Eden Do you know which transports handle back-pressure? IMHO this is a pretty important thing to support. From the code, it looks like `ws` doesn't, for example. EDIT: This seems...
So I'm thinking about back-pressure again. How does the transformer help here without exposing it to the app in the API? I wonder if the whole emitter way of exposing...
I'm coming to the conclusion that until https://github.com/whatwg/streams gets into browsers, it might be best to implement back-pressure over the top of streams1/browser streams. Probably this can be done in...
@aslakhellesoy @3rd-Eden this is what I came up with: https://github.com/davedoesdev/primus-backpressure
Yes - primus-backpressure adds overhead because it has to send status messages letting the sender know how much data is free in the recipient's buffer. There are obviously plenty of...
Just a quick pointer. I used a similar technique to do multiplexing (with back-pressure for each stream separately) over any streams2 `Duplex`: https://github.com/davedoesdev/bpmux It works over Primus (via primus-backpressure).