Does SABnzbd honor newzbins 6 NZBs/minute API restriction?

[FlyveHest]

Simple enough, does SABnzbd handle if I input, lets say, 10 newzbin IDs in 20 seconds?

Does it queue them, or discard them or something else entirely?

[shypike]

The requests are queued and SABnzbd waits the amount of time returned by newzbin's api.

[FlyveHest]

The requests are queued and SABnzbd waits the amount of time returned by newzbin's api.

Excellent, I counted on it, but just wanted to make sure

[shypike]

What happens when you have two SABnzbd clients, and add NZBs to both of them at the same time, linked to the same Newzbin account?

Makes no difference, newzbin keeps sending you wait codes to force the limit.

[DeXeS]

I think sab just try's to grab it till infinity. If the 2 clients are running on the same computer, the computer first does the first request and a 1/1000 second later the other clients request. And if it does happen, your adsl or cable or satellite internet connection can only send 1 data package at a time. So one client alway's faster than the other.

If the clients are running on 2 different computers, the internet connection from newzbin to their ISP can also do one request at the time (but in extreme high speed you can't notice it).

[FlyveHest]

What if one client gets a wait code of 10 seconds, then a second client immediately requests an nzb?

Newzbin will tell the second client to wait for 9 more seconds right? Then both clients will request their nzbs at the same time?

Doesn't the wait time get penalized (increased) if you do that or something?

Logically, it would mean more hits in the "not allowed" timeslot, if SAB A requests, and then SAB B requests 2 seconds later, and get told to wait 10 seconds, and then SAB A requests 10 seconds after its first request, 2 seconds before SAB B is going to request again.

So yes, it could lead to a heightened number of illegal requests, which in turn could lead to a ban.