3 ms·
Ah I think I misread the announcement to mean you were using the OS buffer level information. But if I understand correctly you're just using the buffer size as
by anderspitman 7y ago
Ah I think I misread the announcement to mean you were using the OS buffer level information. But if I understand correctly you're just using the buffer size as a heuristic for the window size, then doing all the logic at the application level?
If that's the case, then implementation-wise these approaches are probably very similar, and window/ACK is the normal way of doing this, and also the pragmatic approach in your case.
- kentonv 7y agoYep. I probably should have gone into more detail on that, and about the problem of slow-app-fast-connection. Oh well.
- dtaht99 7y agoI would hope you'd be amused by: https://blog.apnic.net/2020/01/22/bufferbloat-may-be-solved-but-its-not-over-yet/ https://blog.apnic.net/2020/01/22/bufferbloat-may-be-solved-... and I am curious if you have considered a fq_codel-like approach to message queuing? Sending a whole socketbuf kind of scares me.