On Thu, 17 Mar 2005 13:33:20 -0600, William A. Rowe, Jr.
<[EMAIL PROTECTED]> wrote:
> At 09:57 AM 3/17/2005, Jeff Trawick wrote:
>
> >so I don't misunderstand, what do you consider "buggy platform" that
> >APR can identify?
>
> I don't believe it can identify every scenario you mentioned.
> For what it's worth, any Win32 box that is borked for sendfile
> is also likely borked for acceptex.
>
> What I believe we can do (on platforms we can delve this) is
> determine if the i_dev of the file served is sitting on a non-local
> resource, and cripple sendfile automatically.
>
> It would require some new apr_ intellegence of course.
So far that's 1 of an unknown number of cases we can possibly
identify. We're going to need
EnableSendfile maybe
which means that APR will try to find the situations where sendfile
might not work (e.g., IPv6 or serving from non-local filesystem or LSP
installed or ???? or ????), and not use sendfile in those cases.
If you really know that sendfile can work on your particular box, even
if it is {non-local filesystem, IPv6, whatever}, code
EnableSendfile yes
If APR can't figure out properly (i.e., you still have problems), code
EnableSendfile no
