You are here: Home » Topic » Support for http-request range

Support for http-request range

This topic contains 2 replies, has 2 voices, and was last updated by  tal 9 years, 9 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #2065

    tal
    Participant

    I’ve sent a (RSP style) http-request to firefly (nightly on NSLU2) with a range header so that only part of the song is streamed.

    The start offset works fine (is also displayed correctly in the firefly log) but the end-offset/length is ignored and always all remaining bytes are streamed.

    Background: I really need to fetch the data in small chuncks since otherwise the network stack on PocketPCs is overflown even before I get a chance to drop the connection.

    Thanks
    Thorsten

    #15392

    rpedde
    Participant

    @tal wrote:

    I’ve sent a (RSP style) http-request to firefly (nightly on NSLU2) with a range header so that only part of the song is streamed.

    The start offset works fine (is also displayed correctly in the firefly log) but the end-offset/length is ignored and always all remaining bytes are streamed.

    Background: I really need to fetch the data in small chuncks since otherwise the network stack on PocketPCs is overflown even before I get a chance to drop the connection.

    Thanks
    Thorsten

    hrm. true. It used to fully parse the range header, but I think it got lost somewhere. :/

    I’ve got it on my “things to do before next stable” list. It should be easy enough that I’ll get to it as one of the first things once the db is stable.

    By way of progress report, it’s working now with the new backend, but I still have a deadlock somewhere to chase down. :/

    — Ron

    #15393

    tal
    Participant

    @rpedde wrote:

    hrm. true. It used to fully parse the range header, but I think it got lost somewhere. :/

    I’ve got it on my “things to do before next stable” list. It should be easy enough that I’ll get to it as one of the first things once the db is stable.

    Glad to hear it’ll be fixed 🙂

    Thanks a lot!
    Thorsten

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.