Re^3: Reverse download protocols

Replies are listed 'Best First'.
Re^4: Reverse download protocols by tomasz (Acolyte) on Aug 30, 2021 at 15:40 UTC
That's the whole thing, don't get me wrong... What are reasonable client questions here? The client has to guess the file. So it may ask for something like a hash (as in sha1). Then the server answers yes/no, or gives some hint. So it probably involves some hashing algorithm. I'm not sure...	[reply]
Re^5: Reverse download protocols by hippo (Bishop) on Aug 30, 2021 at 16:32 UTC
It almost sounds like you are talking about caching. If that's the case then there is no need at all to reinvent that particular wheel. See (eg) the If-Modified-Since and Cache-Control headers. 🦛	[reply]
Re^6: Reverse download protocols by tomasz (Acolyte) on Aug 30, 2021 at 16:37 UTC
Sorry, but you seem to have not understood me at all. To clarify even more, the conversation might look like this: Client: hash1? Server: yes Client: hash2? Server: no Client: hash3? Server: yes And so on, until the client knows the file completely, so has no more questions.	[reply]
Re^7: Reverse download protocols by jdporter (Paladin) on Aug 30, 2021 at 17:33 UTC
Re^8: Reverse download protocols by tomasz (Acolyte) on Aug 30, 2021 at 17:41 UTC
Some notes below your chosen depth have not been shown here
Re^7: Reverse download protocols by afoken (Chancellor) on Aug 30, 2021 at 17:40 UTC
Re^8: Reverse download protocols by tomasz (Acolyte) on Aug 30, 2021 at 17:49 UTC


Come for the quick hacks, stay for the epiphanies.
	PerlMonks