Thanks for the report. This was, indeed, a bug that accidentally got
introduced back in July.
I've just installed a new version - 2013.11.26 - of the "LIVE555 Streaming
Media" code that fixes this bug.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
On 11/25/2013 13:54, Bruno Abreu wrote:
What we've noticed is that after the TEARDOWN from each client we can see a
socket left in CLOSE_WAIT state.
That means the client sent FIN, the server stack sent ACK, and nothing
else happened. Because TCP is bidirectional, the server is allowed to
c
Hello Ross,
while trying to replicate a problem that occasionally arises with a small set
of streaming servers, we detected something that might be an issue with
LIVE555.
Those servers are behind a firewall which blocks UDP packets (not under our
control). So the clients request data via TCP, not
