On Wed, Mar 16, 2011 at 1:59 PM, <[email protected]> wrote:
> Mohammed Rashad <[email protected]> wrote on 16.03.2011 09:12:31:
>
> > The ugly way is manually kill the application when a wt application
> > exits. but it is not at all a good solution. becuse after killing
> > the process it will start again within seconds
>
> May be there is a fundamental misunderstanding of how FastCGI is meant to
> work.
> It is normal to have "unused" FastCGI processes hanging around. This
> ensures
> good responsiveness of the application at the first request. If you don't
> do this
>
So what you are saying is its good to have "unused" processes. what is the
need?
How it is beneficial
> you may encounter delays of several seconds when first accessing the site.
>
> Regarding FastCGI vs. http-proxy - I' dont' really get your point about
> "based on Apache".
> You have HTTP proxy and FastCGI on Apache, so this shouldn't be an issue.
>
Yes, I have a http proxy and fastcgi on apache2
>
> Regards, Frank
>
>
>
> ------------------------------------------------------------------------------
> Colocation vs. Managed Hosting
> A question and answer guide to determining the best fit
> for your organization - today and in the future.
> http://p.sf.net/sfu/internap-sfd2d
> _______________________________________________
> witty-interest mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
--
Thanks && Regards
Rashad
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
witty-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/witty-interest
