For how long is downloaded files shared?

[Gew 0]

Hiya.

I knew that playin' the game w/ segmented downloads enabled will cause me to upload while downloading a file. However. Today, I downloaded a file, and after my download was finished, I reckoned uploading the same file ~2h _after_ I had finished my download. Why is this? Is it normal? I presume it's fully normal. However, I'm quite interested in "what's cracking under the hood".

So, how long are downloaded files shared _after_ they've finished downloading? Until I've restarted my DC++ client? A set time?

Regards in adv~

G.

[Gew 0]

I've made a 2nd revision of my post, where I try to be a bit more "on to point" to avoid confusion.

Here goes:

I downloaded file x.mpeg; segmented, of course. Meanwhiles downloading, I, of course, uploaded to several other users. _This I know_ about segmented downloading. However, what I also thought was that when I had finished my download, the file/segments would no longer be available to new(!) users eg. those who search for the file.

Anyways, (hours) after my download had finished, I checked on my tray-minimized client and noticed that I had started uploading the file to a few new(???) users. Is this behaviour normal? And if that is the case, then for how long are my segmented downloads "automatically fully shared"..? A specific time? Or up until I manually close/restart my DC client? Alternatively rename x.mpeg to ie. x.mp3g or something like that. Anyways, I'm really more interested in what's going on "under the hood" here!

To be honest, a point to add is to this is that it could be that I had ..erhm.. well.. disconnected some of the user whom I was uploading to (while I still hadn't finished my download). In this case, could it be that these particular users - whom all of a sudden (hours after I finished my dl) is downloading from me - had automatically been granted a "liana" (upload slot for the particular file) since he's requested it __meanwhile I still had not finished my download__ ; thus being able to reconnect/resume it (later on)even though I'd then be finished downloading? This could then be a considerable explanation to this.

I've tried a few Google strings for some tutorial that explains how DC's partial file sharing works step-by-step, but I haven't found an satisfying answer yet.

I tried executing a 2nd instance of APexDC++ and chose a specific hub to co-connect to, then I searched for "x.mpeg" with new instance of ApexDC++, then %original-instance-of-client% did not come up as result, which was at least semi-comforting; giving some strength to my hypothesis stated above.

Thankful for all answers.

Regards~

[Big Muscle 1]

Such file is shared until you restart your client or until you delete it from Finished downloads window.

About searching, these files won't never be found via classic search. They are found only via TTH search and are not displayed in Search window. They are immediately added as new source.

[Gew 0]

Such file is shared until you restart your client or until you delete it from Finished downloads window.

About searching, these files won't never be found via classic search. They are found only via TTH search and are not displayed in Search window. They are immediately added as new source.

Thanks for your response Big Muscle (and also bigups for the creat client core of yours). I come to realize just about what you just confirmed, but it was a long night's struggle, hrhr. Reading the "unified PFS description" (on various software sites which link to StrongDC++) states:

Partial file sharing

"Allows downloading and uploading parts of file which is being currently downloaded by you or other users. This increases download speed and file expanding over network."

I have to say, this is quite misleading, since it got to me as that [to draw parallels w/ torrent function] my downloaded files would automaticly be "unseeded" after they'd finished. However, when I got those - to me then confusing - uploads started (subject of this thread) I started to think deeply in all sorts of aspects, like that thing with that it could have been some user that I'd disconnected earlier that has got some sort of unique slot for this particular file inplented somewhere in some of the hash data/xmls. I therefor started labbing, ran another client, with no queue/hash (fresh install) and tried connecting to an co-connected hub. Searched for the file, and (like you say) I wasn't listed as a holder.

However, I then tried starting the download from another user, and then ran "search alternatives", and now, it suddenly had me uploading again. I pounded my head and kept brooding what could be the case. I then thought to myself that it could perhaps be the thing with "earlier granted/implented slot for specific user", but based on IP, and therefor I would automatically reconnect even tho on "fresh install", since we were on the same IP. Then, to laborate further, I got to a machine with another IP, and tried from there, same thing, I started uploading. After this (final) test, I had sort of come to the conclusion which you're confirming in your post

Anyways, thanks for the direct and solid answer.

Cheers!