On Monday, September 17, 2012, Gour wrote: > On Mon, 17 Sep 2012 14:59:44 +1000 > David Beitey <[email protected] <javascript:;>> wrote: > > > I'm currently deploying various Python-based WSGI applications via > > uWSGI and haven't had any problems with RHEL 6.2 and Cherokee 1.2.101 > > (latest release version). > > Great...it means there is no need to build master from the Github? > > There's quite a few fixes and improvements in master but 1.2.101 has been fine for me, especially in the uWSGI functionality. In my case I just installed using the EPEL packages for RHEL.
Given the few fixes I submitted or helped submit regarding HTTP method handling and SSL timeouts I'll be looking to use master shortly, however. > > I manage the operation of my long-running processes separately to > > Cherokee (I use Supervisor), but it is possible to configure your > > uWSGI as an information source that Cherokee will boot for you when > > first accessed. > > Iirc, I used Cherokee to do that when I was playing with uWSGI in the > past. > > Actually IIRC, I had experienced an issue with connection timeouts during the period Cherokee was booting the process. The issue was where Cherokee would restart a loading process if not yet ready upon an incoming request. This meant that for multiple concurrent requests, Cherokee would keep killing and restarting the process -- rather than just waiting til the first process started. Unsure if I submitted a bug for this or if it's still a bug in master but worth noting all the same. -- David -- Sent from mobile device - please excuse typos.
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
