|
|
| (2 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| {{Protocols/OSCAR}}
| | [https://gitlab.com/hollerith/cool/-/blob/main/docs/protocols/SNAC/README.md Moved] |
| SNAC notes from another
| |
| <!--
| |
| The SNAC is the unit that sits immediatly above FLAP on most commands, and is the normal contents of the FLAP Data Field for channel 0x02. SNACs are only sent over channel 0x02. Data sent across other channels are not considered complete SNACs. There can be only one SNAC per FLAP command.
| |
| | |
| SNACs are generalized into the following format:
| |
| | |
| Position Size Purpose
| |
| 1 word Family ID
| |
| 3 word SubType ID
| |
| 5 byte Flags[0]
| |
| 6 byte Flags[1]
| |
| 7 dword Request ID
| |
| 11 variable SNAC Data
| |
| | |
| There is no formal declaration of the length of the SNAC data portion (that information must be assumed from the FLAP headers).
| |
| | |
| "Families", identified by the "Family ID", constitute a group of services. These are usually quite large groups.
| |
| | |
| Subtypes are a subdivision of the Families. Each subtype ID is different depending on the specific service or information provided in the data section.
| |
| | |
| Flags are completely optional. They're very rarely used, if at all.
| |
| | |
| Request IDs are 32bit values used to identify non-atomic information. The client can generate completely random reqid's as long as it remembers what the request was for. Often, though, the results of the SNAC are irrelevent, and the reqid's can be forgotten. But, in information-requestion SNACs, it is imparative you remember the reqid you sent because that's the only way to link it to the response! If this is not done, it will be impossible to have more than one pending request of the same SNAC subtype (which is unlikely at best). For server-initiated SNACs, the reqid is ORed with the fixed value -2147483648, and count up to zero from than from zero.
| |
| | |
| Table 2.2.1 lists all documented SNAC types and subtypes.
| |
| | |
| 2.2.1 Notes on SNACs
| |
| | |
| If you have more to add to the list, please do. These are the basics of OSCAR communication, so there's bound to be alot of them!
| |
| | |
| One last note on the subject: never eat SNACs. They're extremely fattening, no matter what the National SNAC Council's television commercials tell you about them. Also, they have been known to cause your limbs to start FLAPing, which often results in unannounced levetation.
| |
| | |
| --> | |
| | |
| SNACs (Simple Network Atomic Communication) are used to represent the protocol messages that are sent between the client and backend. The messages are separated into different categories, called foodgroups. Within each foodgroup there are different kinds of messages related to the category.
| |
| | |
| === Datatype: SNAC__Header ===
| |
| | |
| === Datatype: SNAC__ID ===
| |
| | |
| === Class: SNAC__HEADER_FLAGS ===
| |
| | |
| | |
| | |
| [[Category:Stub]]
| |
| [[Category:AOL]]
| |
| [[Category:AIM]]
| |
| [[Category:Protocols/OSCAR]]
| |
| [[Category:Protocols/OSCAR/SNACs]]
| |
| [[Category:Work_In_Progress]]
| |