| > When the Reset closing the connection arrives, the same shutdown mask is | > set as in TCP. What I thus think you could do as a | > test-for-end-of-connection is to test whether the socket descriptor is | > still read/writeable. | | If it works like TCP, shutdown-for-recv will make the socket always readable, | and will not affect writeability at all, since the sending half may still be | open. As such, I don't think it will solve the problem. DCCP has no half-close (RFC 4340, 4.6), so closing the socket shuts down both the read and the write end (i.e. SHUT_RDWR is set by the kernel) - you could test for this. | Currently, I am assuming that length == 0 means end-of-connection, because I | only use RTP/RTCP, so zero bytes is not a valid packet length. But that's a | little bit ugly. It would be better to use a different solution. There has also been discussion to use 0-sized packets for keep-alive or congestion messages (I hope that this remains talk only). - To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
