<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div>Hey dudes, I think my mail client screwed up some headers and somehow buried my SSL update in the middle of our thread on the list (sure... blame the client!) so I wanted to repost to make sure someone else saw it. I'd really like it if someone could help test this update out a little bit and perhaps even get it moved into trunk? I know Brad is busy retiring... so hopefully this will reach the appropriate parties.
</div><div><br></div><div>The Patch: <a href="http://lists.danga.com/pipermail/perlbal/2007-September/000645.html" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://lists.danga.com/pipermail/perlbal/2007-September/000645.html
</a></div></div></blockquote></div><br>Thanks for bumping. I remember seeing the mail but forgot about it.<br><br>I have tested your patch on my local machine, but it's still blocking. I dug into the IO::Socket::SSL code and it seems that it still does blocking behavior unless you get fancy and manage the reading/writing yourself with the WANT flags.
<br><br>So I spent the last number of hours and took your patch as a start and followed it to the logical conclusion. I've committed my work in revision 708:<br><br> <a href="http://code.sixapart.com/trac/perlbal/changeset/708/">
http://code.sixapart.com/trac/perlbal/changeset/708/</a><br><br>Would love to get some eyes and hands on that. I still don't recommend Perlbal SSL for production load.<br><br>Thanks Greg for motivating this. :)<br><br clear="all">
<br>-- <br>Mark Smith / xb95<br><a href="mailto:smitty@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
smitty@gmail.com</a>