Expose bufferedAmount

[Raynos]

bufferedAmount exposes how much of the data is being buffered right now.

If you want to implement some kind of backpressure mechanism with say high and low watermarks you would need to check bufferedAmount > high mark and apply back pressure then emit some kind of "drain" event when bufferedAmount < low mark.

To do this sockJS needs to expose this information.

[majek]

This is a very good point. I guess you need that both on the client and server side?

[Raynos]

@majek I don't need it on the server. Any compliant node websocket client should already have it.

[arlolra]

do any node websocket clients expose bufferedAmount?

[Raynos]

They should. Websockets do. Not sure of any ws abstraction that exposes it.

[arlolra]

@Raynos should !== do. For instance, ws doesn't. faye does, though it's a constant, maybe indicating nothing is buffered? Anyways, I'm looking for a compliant library, if you come across any.

[Raynos]

@arlolra it's trivial to get access to it by reading socket._writableState.length for TCP sockets

[dmnsgn]

Is there an equivalent concept to bufferedAmount for xhr?

[brycekahle]

Not that I'm aware of.