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

fix EventMachine function call sequence #168

Merged
merged 1 commit into from
Apr 6, 2014
Merged

fix EventMachine function call sequence #168

merged 1 commit into from
Apr 6, 2014

Conversation

esotericaone
Copy link
Contributor

EventMachine what is used in twitter-stream disallows calling start_tls after you start receiving or sending data. The official document describes about it:

An appropriate place to call #start_tls is in your redefined #post_init method, or in the #connection_completed handler for an outbound connection.

In EventMachine, SslBox is set non-null value when StartTls is called, so next start_tls will calls SetTlsParms over Ruby code and it occurs C++ exception what says "call SetTlsParms before calling StartTls".

Current earthquake.gem misses correct function call sequence. This is already represented in #118. I just created this Pull Request with commentary from it.

See also: Google search: "earthquake" "call SetTlsParms before calling StartTls", Twitter search: earthquake "call SetTlsParms before calling StartTls"

jugyo pushed a commit that referenced this pull request Apr 6, 2014
fix EventMachine function call sequence
@jugyo jugyo merged commit f41fae0 into jugyo:master Apr 6, 2014
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