I would like to follow up on the discussion we had in Florence on some
design choices behind OONIB.
In particular the most controversy was around using HTTP or rsync.
Before discussion the pro and contra about one choice over the other it
would be useful to frame
what are exactly the requirements
On Sun, Jul 15, 2012 at 12:56 PM, Arturo Filastò wrote:
> * No resume support (this can be implemented on top of HTTP, we could
> even implement the rsyc algorithm
> on top of HTTP).
Are you sure HTTP doesn't support resume? What does wget -c do?
> Thoughts?
>
> - Art.
>
> [1] https://github.com
Aaron:
> On Sun, Jul 15, 2012 at 12:56 PM, Arturo Filastò wrote:
>> * No resume support (this can be implemented on top of HTTP, we could
>> even implement the rsyc algorithm
>> on top of HTTP).
>
> Are you sure HTTP doesn't support resume? What does wget -c do?
>
I believe this requires the HT
> Contra:
> * No support for deltas (we can use rsych protocol over HTTP if we
> really need this).
It's a little hackish, but I believe there is a 'standard' way to do
this in HTTP also. A client issues a GET (or PUT) request to a
resource, and recieves an Etag that identifies this version of th
On 7/15/12 3:58 PM, Jacob Appelbaum wrote:
>> Are you sure HTTP doesn't support resume? What does wget -c do?
>>
>
> I believe this requires the HTTP: range header and it doesn't provide
> the integrity checking that rsync provides.
It maybe also an application HTTP parameters that contain the la
On 07/15/2012 02:56 PM, Arturo Filastò wrote:
> I would like to follow up on the discussion we had in Florence on some
> design choices behind OONIB.
>
> In particular the most controversy was around using HTTP or rsync.
[...]
> # What properties we would like it to have
> note: these are not or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon 16 Jul 2012 at 02:15, thus spake Ondrej Mikle:
> On 07/15/2012 02:56 PM, Arturo Filastò wrote:
> >
> > # What properties we would like it to have
> > note: these are not ordered.
> > * Efficient even over high latency networks.
> > * Ease of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun 15 Jul 2012 at 10:13, thus spake Tom Ritter:
> > Contra:
> > * No support for deltas (we can use rsych protocol over HTTP if we
> > really need this).
>
> It's a little hackish, but I believe there is a 'standard' way to do
> this in HTTP al
On 7/16/12 2:15 AM, Ondrej Mikle wrote:
> On 07/15/2012 02:56 PM, Arturo Filastò wrote:
>> I would like to follow up on the discussion we had in Florence on some
>> design choices behind OONIB.
>>
>> In particular the most controversy was around using HTTP or rsync.
> [...]
>
>> # What properties w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/17/2012 10:08 PM, Isis wrote:
> On Mon 16 Jul 2012 at 02:15, thus spake Ondrej Mikle:
>> On 07/15/2012 02:56 PM, Arturo Filastò wrote:
>>>
>>> # What properties we would like it to have note: these are not
>>> ordered. * Efficient even over high
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/18/2012 04:46 PM, Arturo Filastò wrote:
> On 7/16/12 2:15 AM, Ondrej Mikle wrote:
>> On 07/15/2012 02:56 PM, Arturo Filastò wrote:
>>> I would like to follow up on the discussion we had in Florence on some
>>> design choices behind OONIB.
>>>
>
11 matches
Mail list logo