Re: [naviserver-devel] naviserver ChangeLog,1.787,1.788

[Stephen D. <sd...@gm...>]

On Fri, Aug 29, 2008 at 2:12 AM, Vlad Seryakov <vl...@cr...> wrote:
>>> +    * tests/http_byteranges.test: Add a couple of tests for ranges on
>>> +    larger files to exercise the file descriptor path rather than the
>>> +    in memory mmap or cache path. Unfortunately, this actually
>>> +    triggers the writer thread and this has no support of ranges,
>>> +    which I guess is where it's actually most needed. TODO...
>>> +
>>
>> I really like last changes, at the same time i need writer support
>> because my tests showed that serving big files with conn threads are
>> waste of resources.
>> At the same time, being able to support range in the writer make sense.
>>
>> And sent email without finishing the thought :-))
>
> Maybe parsing for range should done early enough and saved in the
> request, so whoever then will be sending data will use it.
>
> Just a thought from east coast :-))


I was thinking of adding support for sendfile().

It's different on every platform, so having looked at a few, I was
going to make our interface follow the Solaris senfilev() model which
basically allows an arbitrary number of interleaved memory and file
ranges.  It's an almost exact fit for our byterange code  :-)

Here's the man page:

    http://docs.sun.com/app/docs/doc/816-5172/sendfilev-3ext?a=view

So we'd end up with an array of those sendfilev_t-like structures
describing the data to send. Not sure if they should go in the
conn/request, or...   But maybe it should be a public interface,
unlike the Range struct which is kind of a private thing atm.