Hey Pau, Great work. Some comments below.
2011/9/24 Pau Garcia i Quiles <pgqui...@elpauer.org>: > 1.3 HTTP server forwarding to wthttp webapp > ------------------------------------------- > > This is like case 2.1 I would call this "HTTP server / reverse proxy server forwarding to wthttp webapp". Not all reverse proxy software is in fact also a HTTP server (e.g. HAProxy / squid are only proxy servers), but Apache/NGINX are both. > 2.2 wtfcgi webapp started by cgi-fcgi > ------------------------------------- > > Unless your hosting server has a very strange policy, this scenario should > never happen in production environments. > > The cgi-fcgi tool makes possible to start FastCGI applications from the > command line. See the mention of the 'cgi-fcgi' tool in > http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html#FastCgiExternalServer > > This case is almost the same as 2.1. The only difference is you will need to > make /var/run/wt available before cgi-fcgi (that would be in turn run by > some > other script your host provider mandates) starts the wtfcgi webapp. > I would add a nuance here, that this might be an interesting deployment strategy if you host multiple FastCGI applications, and you want to restart them independently from each other, and independently from the web server. Regards, koen ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ witty-interest mailing list witty-interest@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/witty-interest
