-
Notifications
You must be signed in to change notification settings - Fork 15
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
EventMachine with ssl/TLS. #28
Comments
👍 Sounds good. Would you like to do this at the March meetup? |
Hi Mark, Yeah,15 mins. I think in a case like this where you want to convey a large amount of info, maybe consolidate to 15 minute talk and then maybe a blog post? Let me know what you think. We have a sponsor for March so turnout should be good. |
I’ll see what I can manage. A. On Mon, Mar 2, 2015 at 10:33 AM, MarkT notifications@github.com wrote:
|
Thanks Andrew |
I wouldn’t bank on it. What specifically do you need a connection for? A. On Mon, Mar 2, 2015 at 4:40 PM, MarkT notifications@github.com wrote:
|
Some show-notes: #However, ruby itself uses the openssl compiled with itself: #Not to be confused with the ruby glue library: #This will show the valid ssl_versions #Test for TLSv1_2 context availability |
Shipped! |
I have a talk sketched out which steps through the path taken to implement EventMachine with ssl/TLS.
With the recent security foci, TLS is a 'warming' issue.
So too is the rise of nodeJS alleged performance advantages.
With the release of Ruby 2.2, there are performance opportunities.
Some of which have been factored into the recent EventMachine releases.
Do I need more in a description here?
The text was updated successfully, but these errors were encountered: