Bureaucrats, staff, Administrators
938
edits
Avdump2: Difference between revisions
no edit summary
Jimmydorry (talk | contribs) |
No edit summary |
||
| Line 23: | Line 23: | ||
===Usage=== | ===Usage=== | ||
''' | '''Avdump2''' is a simple [[Wikipedia:Command line interface|command line]] client: | ||
:<tt>AVDump2CL.exe [--<Arg> -<OneLetterArg> ...] <media file/folder> [<media file/folder> ...]</tt> | :<tt>AVDump2CL.exe [--<Arg> -<OneLetterArg> ...] <media file/folder> [<media file/folder> ...]</tt> | ||
| Line 171: | Line 171: | ||
==Auto-creqing== | ==Auto-creqing== | ||
[[Image:Autocreq.gif|thumb|Simple diagram of the way auto-creqing with | [[Image:Autocreq.gif|thumb|Simple diagram of the way auto-creqing with Avdump2 works]] | ||
Avdump2 is the AniDB [[auto-creqing]] system. Some more or less important notes: | Avdump2 is the AniDB [[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 ''UDP 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 ''UDP API Key'' in your [[profile]]'''. All data sent to the server will be logged with IP and uid. | ||
* It is possible to run more than one instance of | * It is possible to run more than one instance of Avdump2 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. | ||
* There is no direct connection between data sent to AniDB and creqs generated. The data received will just be stored for later processing. There is no way to check the current status for a dump. Usually, it should take ''at least 24 hours'' from the moment you dump a file till the data actually changes. If any irregularities occur, or when there is too much data pending, it will take more time. | * There is no direct connection between data sent to AniDB and creqs generated. The data received will just be stored for later processing. There is no way to check the current status for a dump. Usually, it should take ''at least 24 hours'' from the moment you dump a file till the data actually changes. If any irregularities occur, or when there is too much data pending, it will take more time. | ||
* The creqs generated will report the user who sent the data first (for a specific file) as the creqer. | * The creqs generated will report the user who sent the data first (for a specific file) as the creqer. | ||