Protocols/OSCAR/SNAC/FEEDBAG START CLUSTER: Difference between revisions
No edit summary |
|||
Line 13: | Line 13: | ||
They help in cases where multiple instances are online, or when the host is making updates for the client, so the receiving client knows several changes are happening at once. These SNACs have nothing to do with the actual database transactions. In particular, non-receipt of an END_CLUSTER does not cause the database transactions to be rolled back. | They help in cases where multiple instances are online, or when the host is making updates for the client, so the receiving client knows several changes are happening at once. These SNACs have nothing to do with the actual database transactions. In particular, non-receipt of an END_CLUSTER does not cause the database transactions to be rolled back. | ||
the start_cluster end_cluster snacs are optional. if they do not appear in stream of to client, then client should handle each insert delete update snac as it arrives. wait for end_cluster, or after a timeout period before processing all insert, update, deletes. | |||
=== SNAC Header === | === SNAC Header === |
Revision as of 04:30, 27 March 2020
OSCAR Protocol |
Introduction • Terms • Clients |
Basic |
Datatypes • FLAP • SNAC • TLV |
UUIDs • Errors • Tool IDs |
Host Interaction |
Rate Limits • Migration • Messages |
Other Services |
ADMIN • ADVERT • ALERT |
BART • BOS • BUCP • CHAT |
CHAT_NAV |
Tutorials |
Sign On • BART • Rendezvous |
ICBM • Locate • Buddies |
Foodgroups |
OSERVICE (0x0001) |
LOCATE (0x0002) |
BUDDY (0x0003) |
ICBM (0x0004) |
ADVERT (0x0005) |
INVITE (0x0006) |
ADMIN (0x0007) |
POPUP (0x0008) |
PD (0x0009) |
USER_LOOKUP (0x000A) |
STATS (0x000B) |
TRANSLATE (0x000C) |
CHAT_NAV (0x000D) |
CHAT (0x000E) |
ODIR (0x000F) |
BART (0x0010) |
FEEDBAG (0x0013) |
ICQ (0x0015) |
BUCP (0x0017) |
ALERT (0x0018) |
PLUGIN (0x0022) |
UNNAMED_FG_24 (0x0024) |
MDIR (0x0025) |
ARS (0x044A) |
ID | Origin | Name | Foodgroup | Service | Status | Version |
---|---|---|---|---|---|---|
0x0013, 0x0011 | NCD | FEEDBAG__START_CLUSTER | Unspecified | BOS | Active | 4.0 |
The cluster SNACs bracket a set of transactions that should be handled by clients as a group to avoid "flashing" the user's screen.
They help in cases where multiple instances are online, or when the host is making updates for the client, so the receiving client knows several changes are happening at once. These SNACs have nothing to do with the actual database transactions. In particular, non-receipt of an END_CLUSTER does not cause the database transactions to be rolled back. The cluster SNACs bracket a set of transactions that should be handled by clients as a group to avoid "flashing" the user's screen.
They help in cases where multiple instances are online, or when the host is making updates for the client, so the receiving client knows several changes are happening at once. These SNACs have nothing to do with the actual database transactions. In particular, non-receipt of an END_CLUSTER does not cause the database transactions to be rolled back.
the start_cluster end_cluster snacs are optional. if they do not appear in stream of to client, then client should handle each insert delete update snac as it arrives. wait for end_cluster, or after a timeout period before processing all insert, update, deletes.
SNAC Header
Foodgroup | uint16 (word) | 00 13 |
Subgroup | uint16 (word) | 00 11 |
Flags | uint16 (word) | 00 00 |
Request ID | uint32 (dword) | 00 00 00 00 |
@NOTE: ReqID supposedly always 0x00000011
SNAC Data
Name | Type | Notes |
---|---|---|
tlvs | Rest of SNAC array of TLV | Optional qualifying parameters |
FEEDBAG SNACs
|