Jakob Borg 297769ef57 More resilient broadcast handling (fixes #1907) ... My theory is that some error condition on the socket results in it blocking for writes, which maybe also blocks reads... This separates the two into separate services with their own socket, with restarts and retries as appropriates on write timeouts and read/write errors. It should be more robust, hopefully, but I have a hard time testing the actual error conditions...		2015-06-11 15:06:05 +02:00
..
client_test.go	Add mutex logging	2015-04-23 10:54:14 +01:00
client_udp.go	Add mutex logging	2015-04-23 10:54:14 +01:00
client.go	MPLv2	2015-03-17 16:02:27 +01:00
debug.go	MPLv2	2015-03-17 16:02:27 +01:00
discover_test.go	typos and spelling correction	2015-04-29 15:59:47 +02:00
discover.go	More resilient broadcast handling (fixes #1907)	2015-06-11 15:06:05 +02:00
doc.go	MPLv2	2015-03-17 16:02:27 +01:00
packets_xdr.go	Update XDR dependency (fixes #1606)	2015-04-08 14:49:29 +02:00
packets.go	MPLv2	2015-03-17 16:02:27 +01:00