Re: FastCGI & Keep-Alive

Do the thumbnails already exist?  Or are they being created on the fly?

Why would you load images through a php script, unless you absolutely had
to.  You want the browser to cache them, why not just make them real files
and link to the image?  Make the php script just send the browser a dynamic
image link, instead of actually sending the thumbnail?

Or use the affinity patch you mentioned.  I have not looked at that patch,
but shouldn't it use some identifier that is unique to that session?  How
does Apache utilize keepalives, how does it differ from the patch?

Just curious...



On 7:59:34 pm 07/26/06 "Simon" <[email protected]> wrote:
> Hello Folks,
>
> I have a script which loads thumbnail images via a PHP script. Using
> FastCGI PHP with this script creates a problem because there seems to
> be no keep-alive support. I end up with like 40 requests going to 40
> unique FastCGI processes per a single HTML page due to 40 thumbnails
> on the page.
>
> I need all keep-alive requests to go to the same FastCGI process.
> This way all 40 thumbnails, in the example above, would get served
> one after another via the same FastCGI process, not tying up the rest
> of the FastCGI pool. I have looked at Session Affinity patch, is this
> my only option? I do not like the fact that it relies on IP/cookie
> instead of the actual tracking of apache's keep-alive session.
>
> What are my options?
>
> Thank you!
> -Simon
>
>
> ___________________________________
> fastcgi-developers mailing list
> http://fastcgi.com/fastcgi-developers/

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/