Possibility of adding file byte range in issue 75

[George L]

Hello,

In this issue https://github.com/rschildmeijer/deft/issues/75, the
code fix is accepting a complete file, will it be possible to add
support for byte range of a file instead of full file.

Thanks
George

[Roger Schildmeijer]

Hi George,

Do you mean to have support for Range headers? ("HTTP 1.1 does have
the ability to specify ranges in downloads by using the Range header",
source: http://www.west-wind.com/weblog/posts/2004/Feb/07/Using-HTTP-Ranges-to-resume-resume-aborted-downloads)

AFAIK it is not mandatory for clients/servers to support this. But
still, its a good feature, even though we (currently) dont recommend
to use Deft's static file handling in production (look at eg, nginx
instead).

wbr

Roger

Ps. Feel free to file an issue on github (and submit a patch if you
implemented this) regarding the Range http header support. Ds

On 22 Juni, 19:18, George L <georgel2...@gmail.com> wrote:
> Hello,
>
> In this issuehttps://github.com/rschildmeijer/deft/issues/75, the

[George L]

This feature is something similar to netty's zero copy file transfer,
http://docs.jboss.org/netty/3.2/api/org/jboss/netty/channel/DefaultFileRegion.html
.

This feature is mostly helpful in http streaming (apple/adobe/
microsoft). The requests come in as get request urls not as http
headers.

I have been successfully using this feature from netty.

George

On Jun 23, 1:38 am, Roger Schildmeijer <schildmei...@gmail.com> wrote:
> Hi George,
>
> Do you mean to have support for Range headers? ("HTTP 1.1 does have
> the ability to specify ranges in downloads by using the Range header",

> source:http://www.west-wind.com/weblog/posts/2004/Feb/07/Using-HTTP-Ranges-t...)