[CherryPy] #935: Refactor wsgiserver to simplify the use of m2crypto (if one so chooses)

[CherryPy]

#935: Refactor wsgiserver to simplify the use of m2crypto (if one so chooses)
--------------------------------------+-------------------------------------
Reporter: mihai.i...@gmail.com | Owner: fumanchu
Type: defect | Status: new
Priority: normal | Milestone:
Component: CherryPy code | Keywords:
--------------------------------------+-------------------------------------
The bind method of CherryPyWSGIServer is very monolithic. In my case, I
have to use m2crypto instead of pyopenssl, and that means I have to
override the whole function. If the function was broken down into logical
steps, it would be much easier to achieve that.

Attached is a proposal (which also moves the dual-stack activation
_before_ the SSL setup, see #871)

--
Ticket URL: <http://www.cherrypy.org/ticket/935>
CherryPy <http://www.cherrypy.org>
CherryPy - a pythonic, object-oriented HTTP framework

[CherryPy]

#935: Refactor wsgiserver to simplify the use of m2crypto (if one so chooses)
--------------------------------------+-------------------------------------
Reporter: mihai.i...@gmail.com | Owner: fumanchu

Type: defect | Status: closed
Priority: normal | Milestone: 3.2
Component: CherryPy code | Resolution: fixed
Keywords: |
--------------------------------------+-------------------------------------
Changes (by fumanchu):

* milestone: => 3.2
* resolution: => fixed
* status: new => closed

Comment:

Fixed in [2471] and following. The pyOpenSSL code has been moved to its
own module; so has builtin ssl for Python 3 (and any backports). The
separate modules are delegated to via a new
`CherryPyWSGIServer.ssl_adapter` attribute, with `bind` and `wrap`
methods. This should make it fairly simple to integrate M2Crypto. In fact,
if a tested patch could be developed for M2Crypto, we'd very much like to
distribute a module for it in the CherryPy distro.