potential breaking API change around SSL sockets

Hello Yaws community,

Sometime later this week, after Klacke releases 1.94, I'm going to
commit a change for SSL sockets to github master that could
potentially break your code if you match on the current representation
Yaws uses for SSL sockets. Yaws currently internally uses details of a
SSL socket representation that's supposed to be private/opaque to
Erlang's SSL support, so my change will encapsulate SSL sockets within
a {ssl, SslSocket} tuple. I'll also add the yaws_api:get_sslsocket/1
function that returns a socket for SSL sockets or undefined for
non-SSL sockets.

If you have any questions or confusion regarding how this change might
impact any specific parts of your code, feel free to drop me a note by
email and I'll try to help.

Thanks to Fred Dushin for pointing out to me that Yaws was using an
opaque/private SSL socket type.

--steve

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/