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 :-)) Vlad Seryakov 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. > -- Vlad Seryakov [EMAIL PROTECTED] http://www.crystalballinc.com/vlad/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
