strange behaviour...just curious^^

[Blanchimont]

I still can't overcome my curiosity about HOW(did they do that...)

This happened a while back when I was collecting files for the 'Moonlight Mile' batch.
Thanks to a 'seed' somewhere in Finland that was present in all of the files and the sole peer in several, I finally got all of them
However it also involved some of the strangest torrent(client?) behaviour I've encountered so far...

The 'seed' was never bigger than 0.1-2.5%(when starting a download it was 0.1% when connecting and the bottom bar all red(utorrent))
I've seen other torrents behave like that, however...

...it sent pieces in SEQUENCIAL order(from the first piece to the last piece of the file...) and that "0.1-2.5%" followed the 'end' of what was already completed.
To top that...
...Whenever I had computer shuttime(happened a few times) and started utorrent again, that "0.1-2.5%" just placed itself over the 'end' and resumed adding more pieces to it.

This was consistent behaviour in all of the torrents where "it" was the sole other peer...

Like it was DDL instead of torrents(perhaps I should add "in extreme slow motion" as the average speed from "it" was always a consistent 0.3-0.4kb/s...)

As I said, I'm simply curious how a torrent client can be configured like that(the peer list said "it" was using utorrent 1750)...
Or perhaps this is normal behaviour from a web server seed and I just haven't noticed it before?...

Sincerely, Blanchimont

[Zalis_]

I had the same thing happen when trying to DL a Puni Puni Poemi torrent via dht from the now-defunct demonoid tracker -- it sent me the pieces in sequential order, and I was able to open the first file with 40% completion, which you normally can't do with BT. Maybe this is an effect with extremely small-swarm torrents with 1 seeder and 1 peer?