Simon Frei 1f4fde9525 chore(protocol): prioritize closing a connection (#9711) ...

The read/write loops may keep going for a while on a closing connection
with lots of read/write activity, as it's random which select case is
chosen. And if the connection is slow or even broken, a single
read/write
can take a long time/until timeout. Add initial non-blocking selects
with only the cases relevant to closing, to prioritize those.

2024-09-15 21:13:56 +02:00

..

mocks

…

benchmark_test.go

…

bep_extensions.go

…

bep.pb.go

…

bufferpool_test.go

…

bufferpool.go

…

common_test.go

…

compression_test.go

…

compression.go

…

conflict_test.go

…

counting.go

…

debug.go

…

deviceid_test.go

…

deviceid_test.pb.go

…

deviceid.go

…

doc.go

…

encryption_test.go

…

encryption.go

…

errors.go

…

hello_test.go

…

hello.go

…

LICENSE

…

luhn_test.go

…

luhn.go

…

metrics.go

…

mocked_connection_info_test.go

…

nativemodel_darwin.go

…

nativemodel_unix.go

…

nativemodel_windows_test.go

…

nativemodel_windows.go

…

protocol_test.go

…

protocol.go

chore(protocol): prioritize closing a connection (#9711)

2024-09-15 21:13:56 +02:00

vector_test.go

…

vector.go

…

wireformat.go

…