Re: How to make FASTCGI deliver an external file

Ravi Menon wrote:
> [ hopefully I got your doubts well understood]
>
> I can only speak in terms of Linux/FreeBSD env. (but quite likely it
> is similar in Windows too.).
>
> It will be a minor extra 'ipc hop' (via that unix socket) from the
> fast-cgi server back to http server to give a notice to say, "hey go
> serve this file".
Yes. I believe is another record type within the FastCGI protocol itself.
>
> Since the original request came to the fast-cgi server in the first
> place (where some additional custom authorizations were performed if I
> recall your example correctly), then why not serve the file directly
> esp. if there are efficient zero-copy optimisation syscalls like
> sendfile() are available. This approach will be marginally more
> efficient as it saves that extra   call back to the http server (ipc
> cost, context switches and so on...).
Yes.
>
> But I can see some value in re-using exsisting http server capability
> in serving files as you suggest (it does its own default
> authorizations etc.. which you may want to also apply - i.e. basic
> unix permissions and so on). Incidentally apache 2x does use
> sendfile() in  Linux and FreeBSD env. (if my memory serves me right).
OK.

So, as you can see the worth of it, I think it's some to say it loud 
enough so that FastCGI protocol group can her us....
> Engineering...it is all about trade-offs :-)
>
> Ravi
>
>


-- 
Obrigado,
------------------------------------------------------------------------------
                Jose Adriano Baltieri - Analista de Sistemas
                DTI - CENTRO - UNIMEP - Universidade Metodista de Piracicaba
                PIRACICABA - SP - Brasil - Fone : (19) 3124-1858
------------------------------------------------------------------------------

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