Displaying 2 results from an estimated 2 matches for "set_tls_params".
2009 Feb 26
1
0.12.4 dies with call SetTlsParms before
...}
start_tls if @args[:ssl]
super
end
....etc
Did I miss something about a change in the tls-releated portion of the api?
I see that start_tls now takes an optional argument, but that seems unlikely
to be causing the error... Looks like Connection#start_tls calls
EM::set_tls_params followed by EM::start_tls... which seems to be tripping
things up. Am I now required to call EM::start_tls(sig) before
EM::Conn#start_tls? Seems odd... Am I missing something?
BTW, it works fine with 12.2.
--
Colin Steele
www.colinsteele.org
cvillecsteele at gmail.com
Ken Kesey - "Ritual...
2007 Dec 14
21
Some silly benchs (was: 1.9)
Guys,
Just for fun, I tried to see (I know, a silly way to test it) how much
overhead we have calling the C functions of the extensions.
the benchmark script and the results:
http://pastie.caboo.se/128646
The naive C extension:
http://pastie.caboo.se/128647
I compared 1.8.6 (VC6 and mingw builds) against a fresh checkout of ruby trunk.
What I understand from that is 1.9 is slower than 1.8