Queue Memory

dogbite's picture
Description: 
Lets say you add something to the download and the queue is large. You wait and eventually get close to download but... for some reason you had to close slsk. When you start up slsk again you end up last in queue. This is not the case just for the downloader but also for the uploader. If you have a large upload queue and close then start again the upload queue would be different so if someone was first may eventually end up last. I am not entirely sure but slskNS did not had such problems or it did... anyway Perhaps im insane but there should be some way that slsk remembers users download/upload queue line so when i close and run slsk back again it would remember my position. EXSAMPLE: im 700 in the queue i close and in the mean time while i was offline two more users queued the uploader i start back again and slsk should remember that i was before those two users and should put me in front of them. I mean it seems fair. I really hope this would be considered because not only it would make slsk better and more Firm to ground but it will also improve the user download ''experience'' since you know you will eventually get first rather then hopefully get firts to download. Sorry for my english and please leave a comment if this idea is good, bad or maybe possible. Thank you.
0
Your rating: None
1
Average: 1 (1 vote)

Comments

dogbite's picture

Hmm... i cant EDIT so im gonna quickly place it here. This is what happens when the uploader restarts slsk > http://i.imgur.com/GAE9WGQ.jpg?1 < it segments each file by user, at that time there where 23 users downloading from him (or more). Personaly i dont like this, you wait that 22 users download their first file so you can download your first file, then again (depending on the amount of files others have) to download the second. If i would lets say restart slsk at that point it would kick me at the last place (around 500 queue). Seriously if there were some order in the queue SLSK would be 80% better since most of the time thats what slsk does (unless you troll the chat rooms 24/7).

There is probably somebody in the queue who has waited just as long as you. It's really first-come, first-served. I think it would be a challenge for the program to remember your position in the queue. How long of a break to restart would you be taking? I don't think it would be very fair for you to log off for an hour or two and retain your queue position while others have patiently waited their turn in the queue. You might consider donating, so you would be bumped to the front of the line. You could also message the user and ask them to temporarily add you to their userlist and open up another slot.

dogbite's picture

It would be hard to program it, i agree. You dont think it would be fair to me... others would keep their line since the first come, first serve, like you said very nicely, but others who came behind me would stay behind. You would still have to wait, but not that much if something happens to your connection or have to go to work or your ISP restarts every1 connection at midnight (my last IPS did that) or whatever. Now this memory wont be just for me it would be for ALL, so if you queue something before me slsk just remembers that your files have ''priority'' over me and other who came behind you. Same goes for everyone. I AGREE it would not be fair to log off for an hour and retain your position, that user who is downloading in the meantime gets priority over you who is offline. When you come back you wait him to finish, slsk still remembered you are before others. It could be done in some kind of a database table. The table could remember users queue for like 24-48h. If the user removes files he gets removed from the table. Probably im asking to much. I Have few other requests that are more simple and more cosmetic, waiting to see how this one goes first. Thank you for your comment.