SourceResolving a range?

[Marcus Crafter <cr...@managesoft.com>]

Hi All,

Hope all is well.

In our application we've been working on implementing resumed downloads 
using the SourceResolver library. With HTTP, to resume a download one has 
to set a Range: header and specify a (perhaps open) byte range.

Other protocols could support this too, on disk, one has to seek to the 
particular byte, and some ftp servers support it in a similar manner to HTTP
as well.

So, how can we specify it in the call to resolveURI(). I've currently got
a local version of the SourceResolver library that sets a SourceParameter
constant. Currently the constant is defined on the HTTPClientSource object,
but for it to be valid across all protocols I'd like to move this out
somewhere else.

The current format matches that of the HTTP spec, ie. fromBYTE-toBYTE, or 
fromBYTE-, etc. Would everyone be happy with this format as a general range
spec across all of our source implementations?

Also, where should the constant be defined? SourceResolver interface, 
SourceParameters class? Any preferences?

Cheers,

Marcus

-- 
        .....
     ,,$$$$$$$$$,      Marcus Crafter
    ;$'      '$$$$:    Computer Systems Engineer
    $:         $$$$:   ManageSoft GmbH
     $       o_)$$$:   82-84 Mainzer Landstrasse
     ;$,    _/\ &&:'   60327 Frankfurt Germany
       '     /( &&&
           \_&&&&'
          &&&&.
    &&&&&&&:

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org