Stephen asked me to look in to what the new TimeoutMonitor was in CherryPy 3.1. Essentially, it's a part of the new "Web Site Process Bus" (WSPBUS) architecture [1] they've adopted.
In the past, CherryPy did much of its work in a single component _cpengine.py; as part of the work for the new architecture they moved the monitoring code into a "plugin". This allows users/developers to easily override different components of cherrypy's engine, or in our case, customise the timeout logic and behaviour if we so desire. Its behaviour has not effectively changed, although there are a few more messages printed out on depot startup. As for the 408 errors, the CherryPy 3.0.3 wsgiserver would raise a 500 error whenever a socket timeout was encountered. It now properly raises a 408 instead [2]. Any comments? Cheers, -- Shawn Walker [1] http://www.cherrypy.org/wiki/WebSiteProcessBus [2] http://www.cherrypy.org/ticket/810 _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
