Hi
I am constantly geting this message when I am trying to download a song.
Getting "xxxxx.mp3" from xxxxxx
Remotely queued "xxxxx.mp3" from xxxxxx.
Again and again.
I tried sometimes to wait the remote user to start the the upload but this never happened. What can I do for this ? When I used the "nap" cliend with the original napster servers I didn't have this problem
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, a couple of questions: which version of nap are you using (e.g. 1.4.7). Also, do the above messages (Getting..., Remotely queued...) repeat by themselves, or only after you re-request the song? If they repeat periodically, then approximately how many seconds in between?
Generally, "remotely queued" means that the remote user has reached his "upload limit", i.e., he has set a limit on how many songs can be uploaded at any given time. This is normal. The original napster servers did the same thing.
-- Peter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No, the messages appear only when I am trying to get a file. I have a
v1.4.7 client and my linux dist is Debian woody. Ok this is probbably
not o "nap" bug. However some bad (!) clients out there do a "remotely
queued" and with whois I get :
| User: .......
| Class: User
| Line: Unknown
| Time: 9 h 19 m 20 s
| Channels:
| Status: Active
| Shared: 444
| Client: WinMX v2.6
| 0 Downloading, 0 Uploading
I suppose the only solution is to avoid such evil users ?
Thank you !
Panajotis
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This user has probably set their upload limit to 0. Their client responds with "upload limit reached", which nap interprets as in invitation to try again later ("remotely queued"). Maybe I can teach nap not to bother trying if the remote upload limit is indeed 0. I'll look into it. -- Peter
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for your instant response ! The "nap"
client is the coolest and I hope you to improve
it even more. I yesterday found that most
remote clients that give me this error are
WinMX. Perhaps the default settings of the
client are very selfish ? I will install it
on my win98 partition to find out.
Panajotis
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yup, WinMX is a bit selfish by default. I think its upload limit tends to be set to a very small number, such as "2". It is therefore normal that many downloads from such a client would be "remotely queued".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I am constantly geting this message when I am trying to download a song.
Getting "xxxxx.mp3" from xxxxxx
Remotely queued "xxxxx.mp3" from xxxxxx.
Again and again.
I tried sometimes to wait the remote user to start the the upload but this never happened. What can I do for this ? When I used the "nap" cliend with the original napster servers I didn't have this problem
Thanks
Hi, a couple of questions: which version of nap are you using (e.g. 1.4.7). Also, do the above messages (Getting..., Remotely queued...) repeat by themselves, or only after you re-request the song? If they repeat periodically, then approximately how many seconds in between?
Generally, "remotely queued" means that the remote user has reached his "upload limit", i.e., he has set a limit on how many songs can be uploaded at any given time. This is normal. The original napster servers did the same thing.
-- Peter
No, the messages appear only when I am trying to get a file. I have a
v1.4.7 client and my linux dist is Debian woody. Ok this is probbably
not o "nap" bug. However some bad (!) clients out there do a "remotely
queued" and with whois I get :
| User: .......
| Class: User
| Line: Unknown
| Time: 9 h 19 m 20 s
| Channels:
| Status: Active
| Shared: 444
| Client: WinMX v2.6
| 0 Downloading, 0 Uploading
I suppose the only solution is to avoid such evil users ?
Thank you !
Panajotis
This user has probably set their upload limit to 0. Their client responds with "upload limit reached", which nap interprets as in invitation to try again later ("remotely queued"). Maybe I can teach nap not to bother trying if the remote upload limit is indeed 0. I'll look into it. -- Peter
Yup. That was easy to fix. Starting with 1.4.8, nap will just fail such downloads when the remote upload limit is 0. -- Peter
Thanks for your instant response ! The "nap"
client is the coolest and I hope you to improve
it even more. I yesterday found that most
remote clients that give me this error are
WinMX. Perhaps the default settings of the
client are very selfish ? I will install it
on my win98 partition to find out.
Panajotis
Yup, WinMX is a bit selfish by default. I think its upload limit tends to be set to a very small number, such as "2". It is therefore normal that many downloads from such a client would be "remotely queued".