Sektor van Skijlen
Sektor van Skijlen
BTW Changes in the callback function signature is a bad idea. It introduces hard backward ABI incompatibility.
@jeandube I fixed this as one of the first thing I did in SRT :) See `CUDTUnited::close(CUDTSocket* s)`, the section with SRTS_LISTENING state. That was, however, only the first problem,...
@andersc Just note that what is really required here (and possible to be done) is to early disconnect the SRT socket from the multiplexer, not forcefully destroy the multiplexer. Multiplexer...
This has actually nothing to do with C++. This is the UDT's design, which made the socket garbage-collected after being closed, while some activities still need to continue in other...
There's no other way in SRT to share the local port as sharing the Multiplexer. Multiplexer owns the Channel, Channel owns the UDP socket, UDP socket owns the port when...
In the live mode SRT serves only as a throughput. You receive the data as long as they are "in the flow". In order to force stopped reading on the...
It's not "that" shutdown, I meant the "shutdown" like the one done on the TCP socket (see `man 2 shutdown` on POSIX systems). The buffer you are talking about is...
On the sender or receiver side? On the sender side you simply define the time when the packet should be declared as sending time, by default it's the current time...
That could be a good proposal for a statistical value.
I doubt the level of losses itself could be the reason of breaking the connection. You may want to use the caller with the `srt-test-live` application instead, it should display...