Protocols/OSCAR/Services/BART/Tutorials
| 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) |
Getting a User's Buddy Icon
Step #1 - Finding the icon for a user
First the client will need to discover what the Buddy icon BART ID is for the user. Depending on display, the client will want to look inside the USERINFO for either the ICBM__CHANNEL_MSG_TOCLIENT SNAC or BUDDY__ARRIVED SNAC. The USERINFO will contain an array of BART IDs and the client should select the one with the BART__ID_TYPES Class for which it is looking.
Step #2 - Connecting to BART
If the client is not already connected to the BART server it will need to do so.
- Send a OSERVICE__SERVICE_REQUEST to BOSS with the foodgroup of BART.
- Wait for a OSERVICE__SERVICE_RESPONSE from BOSS.
- Using the RECONNECT_HERE tag, connect to the BART server.
- Using the LOGIN_COOKIE tag send a FLAP SIGNON packet, just like connecting to BOSS.
- Send a OSERVICE__CLIENT_ONLINE SNAC to the BART server.
Step #3 - Downloading from BART
Once connected to BART, use the BART__DOWNLOAD2_QUERY SNAC to download as many assets as required.
Step #4 - Display Icon
Display the image.