Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

(#688) Fixed NioWorker to ensure we don't incorrectly report a data received event after an exception... #823

Merged
merged 1 commit into from
Jan 4, 2017

Conversation

cmebarrow
Copy link
Contributor

@cmebarrow cmebarrow commented Dec 14, 2016

…and session closed, as suggested in #688.

I have not been able to think of a way to add a test for this unfortunately. Suggestions welcome.

…e don't incorrectly report a data received event after an exception and session closed.
@cmebarrow cmebarrow changed the title (#688) Fixed NioWorker as suggested in #688 to ensure we don't incorr… (#688) Fixed NioWorker to ensure we don't incorrectly report a data received event after an exception... Dec 14, 2016
@jitsni jitsni merged commit d0ecef5 into kaazing:develop Jan 4, 2017
@cmebarrow cmebarrow deleted the issue_688_tcp_event_order branch January 14, 2017 02:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants