Skip to content
This repository was archived by the owner on Nov 28, 2019. It is now read-only.
This repository was archived by the owner on Nov 28, 2019. It is now read-only.

isOpen on AsyncronousSocketChannel fails #109

@jasonmartens

Description

@jasonmartens

Really excited to see this library exists!

I've been playing around with the server, and when I accept a connection from a netcat client, after terminating the connection isOpen remains true, and there doesn't seem to be any way on the server to tell that the connection has disappeared. If I have a loop running to continue reading data from the socket, then it will spin forever. Example application is here:
https://gist.github.com/jasonmartens/91819c538608497a4dbfa547df334b98

After running, I can send data using nc -v 127.0.0.1 1337, then type in a few characters followed by ctrl-c or ctrl-d. Then the server will loop endlessly (limited here to 100) reading 0 byte buffers.

I would expect either isOpen to change to false, or no bytes to be available to read.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions