bug: count is not always 0 when io.EOF is encountered #2

Open
opened 2018-08-06 22:38:19 +00:00 by coolaj86 · 0 comments
Owner

Currently the telnet reader quits when EOF is encountered.

This happens to work correctly with Telnet, but may not work correctly with piped netcat or other clients that send the EOF fast enough for it to end up in the read buffer.

Currently the telnet reader quits when EOF is encountered. This happens to work correctly with Telnet, but may not work correctly with piped netcat or other clients that send the EOF fast enough for it to end up in the read buffer.
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coolaj86/chat.go#2
No description provided.