546
edits
UDP API Definition: Difference between revisions
m
→General
Epoximator (talk | contribs) (→MYLISTADD: Add file to mylist: cached values per anime also fixed) |
Epoximator (talk | contribs) m (→General) |
||
| Line 31: | Line 31: | ||
=== General === | === General === | ||
The network communication is ''packet'' and ''line'' based. Each ANIDB API command is exactly one UDP packet containing one line. Results are sent as one packet but may consist out of multiple lines. A return value always starts with a 3 byte result code followed by a human redable version of the result code. Be aware that important data fields may be returned directly after the return code (see: 200,201,271,272,504). | The network communication is ''packet'' and ''line'' based. Each ANIDB API command is exactly one UDP packet containing one line. Results are sent as one packet but may consist out of multiple lines. A return value always starts with a 3 byte result code followed by a human redable version of the result code. Be aware that important data fields may be returned directly after the return code (see: 200,201,271,272,504). | ||
The meaning for all result codes can be found in this document. If there is more than one entry returned, it's one entry per line. Lines are terminated by a <tt>\n</tt> (no dos linefeed <tt>\r</tt>). The elements of a format string are seperated by a "|" character. | The meaning for all result codes can be found in this document. If there is more than one entry returned, it's one entry per line. Lines are terminated by a <tt>\n</tt> (no dos linefeed <tt>\r</tt>). The elements of a format string are seperated by a "|" character. | ||
<tt>{three digit return code} {str return string}\n</tt><br> | |||
<tt>{data field 0}|{data field 1}|...|{data field n}</tt> | |||
'''IMPORTANT:''' | '''IMPORTANT:''' | ||