546
edits
UDP API Definition: Difference between revisions
Jump to navigation
Jump to search
→General
Epoximator (talk | contribs) |
Epoximator (talk | contribs) |
||
| Line 42: | Line 42: | ||
* All commands except PING, ENCRYPT, ENCODING, AUTH and VERSION '''requires''' login, meaning that the ''session tag'' must be set (<tt>s=xxxxx</tt>). | * All commands except PING, ENCRYPT, ENCODING, AUTH and VERSION '''requires''' login, meaning that the ''session tag'' must be set (<tt>s=xxxxx</tt>). | ||
* A client should ignore any additional trailing data fields it doesn't expect. Additional fields are going to be added to the output of some commands from time to time. Those additional fields will simply be appended to the end of the existing output. A client should be written in a way so that it is not affected by such new fields. | * A client should ignore any additional trailing data fields it doesn't expect. Additional fields are going to be added to the output of some commands from time to time. Those additional fields will simply be appended to the end of the existing output. A client should be written in a way so that it is not affected by such new fields. | ||
* Due to the length constraints of an UDP package the replies from the server will never exceed 1400 bytes. String fields will be truncated if necessary to ensure this. No warnings are given when this happens. | * Due to the length constraints of an UDP package (over PPPoE) the replies from the server will never exceed 1400 bytes. String fields will be truncated if necessary to ensure this. No warnings are given when this happens. | ||
* A client should handle all possible return codes for each command. | * A client should handle all possible return codes for each command. | ||
** Possible return codes for '''all commands''': | ** Possible return codes for '''all commands''': | ||