5
edits
Avdump: Difference between revisions
→Autocreqing
m (→Send to) |
|||
| Line 144: | Line 144: | ||
[[Image:Autocreq.gif|thumb|Simple diagram of the way autocreqing with avdump works]] | [[Image:Autocreq.gif|thumb|Simple diagram of the way autocreqing with avdump works]] | ||
Avdump is now part of a new autocreqing system. Some more or less important notes: | Avdump is now part of a new [[autocreqing]] 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 password'' 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 password'' 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.'' | ||