Node:Some Client-specific Aux-Item Types, Next:, Previous:Importing and Exporting E-Mail, Up:Top



Some Client-specific Aux-Item Types (informative)

This appendix contains some contributed information from client writers about some of the aux-item types that they use. This information may be updated at any time by the client writers. How much the client writer cares about backward compatibility when they make changes to these aux-item types may be beyond the control of the authors of the Protocol A specification.

If any of the aux-item types defined here becomes widely used by different clients, they should probably be standardized and moved to the Aux-Item Types chapter.


elisp-client-read-faq [10000] (letterbox)
This item indicates FAQs that the user has read. Data is a decimal number indicating the conference for which a FAQ has been read, followed by a space character and a second decimal number indicating the text number of the FAQ. In the future, additional data may be defined; clients should be prepared to accept and ignore a space and any trailing data that may follow the second number.

Note that aux-items of this type should always be secret since they may contain information about texts of conferences that are not publicly visible.

A few examples might clarify what the data may look like:

459 11215
FAQ in text 11215 for conference 459 has been read.
459 11215 garbage
FAQ in text 11215 has been read. Clients must ignore the trailing garbage. Note that clients are not allowed to create aux-items of this format, but they should be prepared to handle them correctly.

This aux-item is specific to the elisp client. Other clients are not required to use or understand this item type.

elisp-client-rejected-recommendation [10001] (letterbox)
This item indicates a rejected membership recommendation. Data is a decimal number indicating the conference for which the recommendation was rejected. In the future, additional data may be defined; clients should be prepared to accept and ignore a space and any trailing data that may follow the second number.

Note that aux-items of this type should always be secret since future extensions may contain sensitive data.

A few examples might clarify what the data may look like:

459
A recommendation for conference 459 has been rejected.
459 garbage
A recommendation for conference 459 has been rejected. Clients must ignore the trailing garbage. Note that clients are not allowed to create aux-items of this format, but they should be prepared to handle them correctly.

This aux-item is specific to the elisp client. Other clients are not required to use or understand this item type.