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
Aaron:
On Sun, Jul 15, 2012 at 12:56 PM, Arturo Filastò a...@torproject.org 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
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 the
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 last
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
Hello.
During the last week Damian merged my patches that implement loadconf saveconf
wrapper methods[1][2] in Stem. I am currently working on implementing the router
descriptors (from the network status documents). I should have
something ready for
review by tuesday. Once that is done, I'll
