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

Add TCP alert handler #873

Merged
merged 2 commits into from
Sep 7, 2016
Merged

Add TCP alert handler #873

merged 2 commits into from
Sep 7, 2016

Conversation

rossmcdonald
Copy link
Contributor

@rossmcdonald rossmcdonald commented Sep 6, 2016

Required for all non-trivial PRs
  • Rebased/mergable
  • Tests pass
  • CHANGELOG.md updated
  • Sign CLA (if not already signed)

return
}

conn, err := net.Dial("tcp", tcp.Address)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible to reuse the same TCP connection and use the Write method to send individual packets for each event? Not sure if that would break the server side.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had considered that, but it seemed like it would be a pretty large undertaking. I'm assuming it would require some connection pooling per handler, with some mechanisms for checking the health of the connections (and maybe closing connections after a longer period of inactivity). Not sure if that's way off base or not, though.

I'd be up for discussing it more in depth offline if you have some time.

@nathanielc nathanielc merged commit 1a705d4 into master Sep 7, 2016
@nathanielc nathanielc deleted the ross-tcp-alert branch September 7, 2016 20:57
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.

3 participants