23
edits
Avdump: Difference between revisions
→Auto-creqing
mNo edit summary |
|||
| Line 156: | Line 156: | ||
Avdump is now part of a new [[auto-creqing]] system. Some more or less important notes: | Avdump is now part of a new [[auto-creqing]] system. Some more or less important notes: | ||
* To be able to use this feature you’ll need an AniDB account and you have to define the ''api key'' in your [[profile]]. All data sent to the server will be logged with IP and uid. | * To be able to use this feature you’ll need an AniDB account '''and you have to define the ''api key'' in your [[profile]]'''. All data sent to the server will be logged with IP and uid. | ||
* Communication between client and server is ''one-way'' (except session init/refresh); the client does not receive any confirmation for sent data. This means that there is no guaranty that all the dumps you send will arrive at the server and stored in the database, and there is no way to check this. ''From version 0.31 it's possible to make Avdump wait for confirmation from the server by using the -o switch.'' | * Communication between client and server is ''one-way'' (except session init/refresh); the client does not receive any confirmation for sent data. This means that there is no guaranty that all the dumps you send will arrive at the server and stored in the database, and there is no way to check this. ''From version 0.31 it's possible to make Avdump wait for confirmation from the server by using the -o switch.'' | ||
* It is possible to run more than one instance of Avdump at once, but not more than ten will work OK. At the moment ''only 10 sessions per ip are allowed by the server'', meaning the eleventh instance will terminate the first. | * It is possible to run more than one instance of Avdump at once, but not more than ten will work OK. At the moment ''only 10 sessions per ip are allowed by the server'', meaning the eleventh instance will terminate the first. | ||