Be able to determine to continue waiting for a free slot...

[giga_d]

Would it be a good idea to be able to see how many upload slots and what other people are downloading from another user if your are also waiting to download something from that user and there are no slots available?

One would be able to manage whether it would be a good idea to either keep waiting until a slot is available or if it is better to come back at a later time or not bother at all. After all waiting for someone to finish downloading large files and then the user goes offline after waiting to start or even continue downloading something is not everyone's desired outcome. Of course one would be doing other things in the mean time and I assume (like me) download and upload in the meantime - not just staring at the screen waiting. Also one cannot determine the speed at the download rate of the other slot user, and variables such as whether they stop downloading, go offline etc... but in my particular case if I could see there was a long wait I could manage the use my internet connection for other purposes which requires exiting the DC++ program altogether for bandwidth purposes. Just a thought.

[BSOD2600]

Would it be a good idea to be able to see how many upload slots and what other people are downloading from another user if your are also waiting to download something from that user and there are no slots available?

Dude, you seriously need to work on making your sentences more understandable .

You can already see how many slots a person has by the S: tag. When you search, you can also see how many are in use. Read, the meaning of the V++ tag

As for seeing where are in their upload queue, this is not possible since DC++ has no upload queue system. Its random.

[giga_d]

Enlightened and thankful for it, the accompanying faq didn't show me anything about that nor did I even realise what it was for to even think it was linked. Although the essence of the post was not only the upload slots, but also to determine how long you will have to wait by being able to see the size of files being downloaded by other users from the target source.

As for seeing where are in their upload queue, this is not possible since DC++ has no upload queue system. Its random.

I realised there was no upload queue system thats why this post is in the Features forum. Being that it is random; you can request a file from a user and have as much priority of getting the next available slot as the person who has been waiting longer than you for a slot? I wouldn't say thats the best system but i'm a total newb so there may be a good reason for this that I don't know about.

[GargoyleMT]

Being that it is random; you can request a file from a user and have as much priority of getting the next available slot as the person who has been waiting longer than you for a slot? I wouldn't say thats the best system but i'm a total newb so there may be a good reason for this that I don't know about.

Sure, drop "priority" though - DC++ itself is strictly first-come-first-serve.

There's nothing to report to the remote end - any downloader could disconnect at any time, or (at the other extreme) be downloading your entire library of shared files.

Waiting for slots is a fact of life with the DC Protocol, please understand that.

[giga_d]

Sure, drop "priority" though - DC++ itself is strictly first-come-first-serve.

There's nothing to report to the remote end - any downloader could disconnect at any time, or (at the other extreme) be downloading your entire library of shared files.

Thank you for confirming what the previous poster stated. Being that this is the features forum, would this be something that need changing?

Waiting for slots is a fact of life with the DC Protocol, please understand that.

Reading through what I previously wrote, nothing I said indicated I didn't already know that, making you sound slightly arrogant from that remark.

[GargoyleMT]

Thank you for confirming what the previous poster stated. Being that this is the features forum, would this be something that need changing?

Well, the natural way to change it is to add an upload queue. That's a rejected feature.

Reading through what I previously wrote, nothing I said indicated I didn't already know that, making you sound slightly arrogant from that remark.

You want to know how long it'll take you to get a slot, so you sound like you're impatient - thus my comment.

[giga_d]

That's a rejected feature.

What was the reason to not implement it?

so you sound like you're impatient - thus my comment.

Doesn't change the fact it's a bit arrogant, especially since it doesn't add anything to the discussion and is unecessary. Besides, I have valid reason to be able to determine the size of files being downloaded from the target source in the first post. Not so much impatience as it is a way for me to determine how best to use my bandwidth when downloading wouldn't be feasible.

Regards.

[GargoyleMT]

What was the reason to not implement it?

You'll have to ask arne. It was not my decision, and not within my power to reverse.

Besides, I have valid reason to be able to determine the size of files being downloaded from the target source in the first post.

Then use one of the DC++ mods that supports an upload queue. Namely, BCDC.

[Sedulus]

not only is there no upload queue, there is no file queue either.. once someone has acquired a slot, he can keep requesting files for all eternity (unless the connection is (un)intentionally broken).
of course a file queue could also be implemented.. but this would break compatibility. this approach has the additional difficulty that you'd need serious convincing powers (or rather, very compelling arguments).

those compelling arguments are nowhere to be found in your post (I'll also reiterate your post is horribly vague).

I don't see where your problem is...
if you're a good hub user, you are online 24/7, and have no trouble waiting for that file to appear on your drive whenever that may happen
selecting files because of slot availability sounds rather odd to me. "I don't want music X if I have to wait 2 days for it, I'll listen to music Y instead, and I don't have enough HD space for both"?

[giga_d]

Then use one of the DC++ mods that supports an upload queue. Namely, BCDC.

Thanks, you could of said that from the beginning.

those compelling arguments are nowhere to be found in your post (I'll also reiterate your post is horribly vague).

Yeah sorry about that, it is difficult to understand the question. I can see that it is not necessary to implement a queing system. Although technically I just wanted to see the size of files being downloaded from the target source.

I don't see where your problem is... if you're a good hub user, you are online 24/7

Sorry i'm not. Seeing as this is the features forum, I thought asking a relatively simple question on implementing a feature to see the size of files other users are downloading from the target source would be feasible. I now know it is available in another mod apparently so its ok.

[GargoyleMT]

Thanks, you could of said that from the beginning.

And you could've found BCDC and it's upload queue capability on your own.

Yeah sorry about that, it is difficult to understand the question. I can see that it is not necessary to implement a queing system. Although technically I just wanted to see the size of files being downloaded from the target source.

You want this feature because you're the one with the files, and you want to see who is trying to get files from you, and what files they've requested? Your messages read as though you're the downloader, and want to see what files other people are downloading from the user you've got queued - that makes a big difference in how the feature is received.