From: ke h. <ke...@re...> - 2006-08-29 04:13:29
|
thanks Claes... thats just the kind of confident response I was hoping for ;-).. BTW, I listened to your BSD radio interview...glad to hear yaws =20 getting the word out to the masses. If you can call the BSD =20 community massive...all is relative when your sitting on an erlang =20 rock. ;-) The most important thing I learned from the audiocast is that Claes =20 is not pronounced "Claws". I doubt I can yet pronounce your name =20 correctly, but I do know that "Claws" isn't correct ;-) thanks again, ke han On Aug 28, 2006, at 8:20 PM, Claes Wikstr=F6m wrote: > ke han wrote: >> I'm about to develop a yaws app which will serve most of its pages =20= >> as as HTTPS. Pretty much everything expect the home page. >> I would like to know any concerns/limitations of the underlying =20 >> SSL used by Yaws. >> I have seen old erlang maillist posts such as: >> http://erlang.org/ml-archive/erlang-questions/200311/msg00252.html >> This post seem to indicate the issue is needing to tune erlang to =20= >> handle a large number of sockets. >> Anything else I should know about for handling large numbers of =20 >> HTTPS requests? > > The OTP SSL implementation isn't the best in town. It's ok > but it has had a number of obscure bugs over the years. > we've built several high traffic SSL sites with yaws + ssl > and also submitted a number of small but crucial ssl bugfixes > to the otp group. > > As it stands now, all should be ok. > > As for that old post that had FD_SETSIZE set to 256, it > doesn't sound really up to date. Also, looking at the code > in esock_poll.c it seems as if OTP ssl now use poll instead > of select() so, the number of SSL sockets should really be > limited by the max num open fds for that unix process which > is tunable to very high number in most modern unices. > > > /klacke > > > > --=20 > Claes Wikstrom -- Caps lock is nowhere and > http://www.tail-f.com -- everything is under control > cellphone: +46 70 2097763 |