Sorry for my long absence!
And thank you all for the interest, I'd like to give some clarifications, I've relly made an effort to make my english and my thought understandable and (hopefully) clear.
Well, the only difference between normal shutdown and "soft" is 2)finish upoloading the chunks that are currently uploading
.
Actually I think that the possibility to shut down the computer
too makes the difference...
when I have to go away and shut down the computer, I'd rather use a soft shutdown.
Well, you suggest I leave it on 15 min longer, finish some uploads but accept no more. If instead I leave it running at full for these 15 min, I could upload more in this time, maybe even finish someones gap in another rare chunk that in "soft shutdown mode" would have been rejected. So I think your logic is flawed. 
well, not accepting new downloads would concentrate the band on the remainders, but wont reduce it, so the bytes uploaded in those 15min would be the same "volume"
but entirely dedicated to chunk completion. (AFAIK uncomplete chunks are not shared)
[...]
Beside the fact that there might be someone that allow only to download with 0.1kb - that would take hours till this chunk is finished.
I have never seen a stable connection that slow... but I see it's not impossible, I suppose that a time limit is the only way to handle slow downloaders
All together I find this a nice idea, but I prefer to leave my aMule runing 24/7. :p
Two times thankyou!!
Nice idea but I doubt they will add anything as most leecher may find this effective and finish downloading and then shutdown when source exchange begins as chunk is published in network.
I'm not sure that I've understood, all the point is about completing uploads before shutting down, not downloads...
But you can use the alternative just disconnect from the network it can be KAD or eD2k and you won't get new uploads then when upload is complete shutdown aMule. While you are disconnected it is possible to share still.
I've tried, this wont limit the downloads to the currently uploading chunks: after those the uploads continue, maybe until entire files are completed, I don't know.
Maybe a way to do it would be to rise the band per client to all the available band, and then shut down when the last client has finished with his chunck, but this would imply my presence, and of course I don't want that.
i think i get the author's idea.
it is to check before shutdown if there is some uploaders that "almost got" some chunk (say >90%, or <0,5 mb left), to close all other connections, to give all bandwidth to these, finish them, and to finally shutdown.
Actually my idea is (possibly) to complete all the uploading chunks, I don't think that spreading around the net loads of incomplete chunks is "healthy" for the net
this would be helpful for those with hypertrophied conscience who takes every shutdown as a crime. this feature will lighten their guilt.
the simpler way to do it is to pop-up a text "it's okay to disconnect at will" every amule's start. may be such a therapy would be even more effective.
My hypertrophic conscience is double faced... I'd like if YOU all used a "soft" shutdown
More seriously I think that we all would benefit from this modification, if many of us used it.
