Hey lwerndly, have been a long time MyAnime user and have just shifted to JMM and really excited by what I'm seeing. Problem I am having is with constant AniDB Ban's whilst importing my collection. After looking through the AniDB UDP API wiki I found this nugget:
Connection Problems
There are many ways for a client to end up banned or the API might currently be handling too many concurrent connections. If a client does not get any reply to an AUTH command it should start to increase the retry delay exponentially with every failed login attempt. (i.e. try again after 30 seconds if the first login attempt failed, if the second fails too retry after 2 minutes, then 5 minutes, then 10 minutes, then 30 minutes, ... until you reach a retry delay of ~2-4h.)
and...
Flood Protection
To prevent high server load the UDP API server enforces a strict flood protection policy.
Pretty sure you're well across this but it's going to be pretty hard going if we're constantly getting bans from AniDB when importing our collections. This may not be an issue later on as we'll only be doing the occasional call for new eps, but it's quite painful during the initial call. Understand JMM is still Alpha which is why I'm trying to make this as detailed and constructive as possible.
Does JMM have an auto-delay function once it's been banned? Or should I raise this as an issue on google code?
Connection Problems
There are many ways for a client to end up banned or the API might currently be handling too many concurrent connections. If a client does not get any reply to an AUTH command it should start to increase the retry delay exponentially with every failed login attempt. (i.e. try again after 30 seconds if the first login attempt failed, if the second fails too retry after 2 minutes, then 5 minutes, then 10 minutes, then 30 minutes, ... until you reach a retry delay of ~2-4h.)
and...
Flood Protection
To prevent high server load the UDP API server enforces a strict flood protection policy.
- Short Term:
- A Client MUST NOT send more than 0.5 packets per second (that's one packet every two seconds, not two packets a second!)
- The server will start to enforce the limit after the first 5 packets have been received.
- Long Term:
- A Client MUST NOT send more than one packet every four seconds over an extended amount of time.
- An extended amount of time is not defined. Use common sense.
Pretty sure you're well across this but it's going to be pretty hard going if we're constantly getting bans from AniDB when importing our collections. This may not be an issue later on as we'll only be doing the occasional call for new eps, but it's quite painful during the initial call. Understand JMM is still Alpha which is why I'm trying to make this as detailed and constructive as possible.
Does JMM have an auto-delay function once it's been banned? Or should I raise this as an issue on google code?