Protocols/OSCAR/Foodgroups/BART - Revision history

AD: /* Class: BART__ID_TYPES */

2020-03-24T12:42:09Z

Class: BART__ID_TYPES

← Older revision		Revision as of 12:42, 24 March 2020
Line 96:		Line 96:
	\| NOT CURRENTLY DOCUMENTED		\| NOT CURRENTLY DOCUMENTED
	\|-		\|-
	\| ~~BART__TYPES_BIG_ICON~~		\| BART__TYPES_BUDDY_ICON_BIG
	\| 0x0C		\| 0x0C
	\| SWF		\| SWF

AD at 07:30, 22 March 2020

2020-03-22T07:30:13Z

← Older revision		Revision as of 07:30, 22 March 2020
Line 15:		Line 15:

	Having a Buddy icon with opaque data of 0x0201d20472 means the user has explicitly chosen to have no Buddy icon. This is different then not having a Buddy icon. This ID should be treated specially and does not need to be fetched from BART (although BART will return an empty GIF). This was done so clients could tell when they upgraded from old style Buddy icons to BART Buddy icons. This special ID should NOT be used for other BART types.		Having a Buddy icon with opaque data of 0x0201d20472 means the user has explicitly chosen to have no Buddy icon. This is different then not having a Buddy icon. This ID should be treated specially and does not need to be fetched from BART (although BART will return an empty GIF). This was done so clients could tell when they upgraded from old style Buddy icons to BART Buddy icons. This special ID should NOT be used for other BART types.

			== SNACs ==
			{{Protocols/OSCAR/Foodgroups/BART/SNACs}}

	== BART_ID ==		== BART_ID ==
Line 299:		Line 302:
	\| BART IDs to fetch		\| BART IDs to fetch
	\|}		\|}

	~~== SNACs ==~~
	~~{{Protocols/OSCAR/Foodgroups/BART/SNACs}}~~

	[[Category:Stub]]		[[Category:Stub]]

AD at 07:28, 22 March 2020

2020-03-22T07:28:17Z

← Older revision		Revision as of 07:28, 22 March 2020
Line 278:		Line 278:
	\|}		\|}

			=== Datatype: BART__ID_TO_USERNAME ===

			This links a BART ID and a username.

			{\| class="wikitable"
			! Name
			! Type
			! Notes
			\|-
			\| username
			\| string08
			\| User who is using the asset
			\|-
			\| numIds
			\| uint8 (byte)
			\| Number of assets being requested
			\|-
			\| ids
			\| Array of [[Protocols/OSCAR/Foodgroups/BART#Datatype:_BART_ID\|BART__ID]] length numIds
			\| BART IDs to fetch
			\|}

	== SNACs ==		== SNACs ==

AD at 07:26, 22 March 2020

2020-03-22T07:26:31Z

@@ Line 212: / Line 212: @@
 |}
-== Class: BART__REPLY_CODES ==
+== For Query Responses ==
 These are the result codes of uploads, downloads, and queries.

AD at 07:21, 22 March 2020

2020-03-22T07:21:28Z

Show changes

AD at 07:17, 22 March 2020

2020-03-22T07:17:44Z

@@ Line 55: / Line 55: @@
 | 0xC0
 | BART is disallowed by hash
 |}

AD at 07:12, 22 March 2020

2020-03-22T07:12:56Z

← Older revision		Revision as of 07:12, 22 March 2020
Line 16:		Line 16:
	Having a Buddy icon with opaque data of 0x0201d20472 means the user has explicitly chosen to have no Buddy icon. This is different then not having a Buddy icon. This ID should be treated specially and does not need to be fetched from BART (although BART will return an empty GIF). This was done so clients could tell when they upgraded from old style Buddy icons to BART Buddy icons. This special ID should NOT be used for other BART types.		Having a Buddy icon with opaque data of 0x0201d20472 means the user has explicitly chosen to have no Buddy icon. This is different then not having a Buddy icon. This ID should be treated specially and does not need to be fetched from BART (although BART will return an empty GIF). This was done so clients could tell when they upgraded from old style Buddy icons to BART Buddy icons. This special ID should NOT be used for other BART types.

	=== Class: BART__ID_FLAGS ===		== Datatype: BART__ID ==
			X

			== Class: BART__ID_FLAGS ==

	These are the flags used by the client to detect how the BART ID should be processed.		These are the flags used by the client to detect how the BART ID should be processed.
Line 54:		Line 57:
	\|}		\|}

	=== Class: BART__ID_TYPES ===		== Class: BART__ID_TYPES ==

	These are all the different BART ID types that are known about and their restrictions.		These are all the different BART ID types that are known about and their restrictions.

AD at 07:12, 22 March 2020

2020-03-22T07:12:12Z

← Older revision		Revision as of 07:12, 22 March 2020
Line 9:		Line 9:
	{{Protocols/OSCAR/Foodgroups/BART/Description}}		{{Protocols/OSCAR/Foodgroups/BART/Description}}

			== Introduction ==
	For some items, the actual assets are downloaded using the BART system and in other cases, just descriptive XML files are used. Once a BART item is downloaded, it is basically cached FOREVER by the client, so updating requires publishing a new BART item. This is especially important when the BART item is an asset. When the BART item is a descriptive XML file, only the XML file is cached forever and any assets it refers to can use different caching schemes determined by the client.		For some items, the actual assets are downloaded using the BART system and in other cases, just descriptive XML files are used. Once a BART item is downloaded, it is basically cached FOREVER by the client, so updating requires publishing a new BART item. This is especially important when the BART item is an asset. When the BART item is a descriptive XML file, only the XML file is cached forever and any assets it refers to can use different caching schemes determined by the client.

AD: /* Class: BART__ID_FLAGS */

2020-03-22T07:11:06Z

Class: BART__ID_FLAGS

@@ Line 47: / Line 47: @@
 | 0x80
 | Used in OSERVICE__BART_REPLY; BART says use this ID instead for the matching type
 |}
 {{Protocols/OSCAR/Foodgroups/BART/SNACs}}

AD at 06:56, 22 March 2020

2020-03-22T06:56:04Z

← Older revision		Revision as of 06:56, 22 March 2020
Line 14:		Line 14:

	Having a Buddy icon with opaque data of 0x0201d20472 means the user has explicitly chosen to have no Buddy icon. This is different then not having a Buddy icon. This ID should be treated specially and does not need to be fetched from BART (although BART will return an empty GIF). This was done so clients could tell when they upgraded from old style Buddy icons to BART Buddy icons. This special ID should NOT be used for other BART types.		Having a Buddy icon with opaque data of 0x0201d20472 means the user has explicitly chosen to have no Buddy icon. This is different then not having a Buddy icon. This ID should be treated specially and does not need to be fetched from BART (although BART will return an empty GIF). This was done so clients could tell when they upgraded from old style Buddy icons to BART Buddy icons. This special ID should NOT be used for other BART types.

			=== Class: BART__ID_FLAGS ===

			These are the flags used by the client to detect how the BART ID should be processed.

			{\| class="wikitable"
			! Name
			! Value
			! Notes
			\|-
			\| BART__FLAGS_KNOWN
			\| 0x00
			\| NOT CURRENTLY DOCUMENTED
			\|-
			\| BART__FLAGS_CUSTOM
			\| 0x01
			\| This is a custom blob; the opaque data will also be 16 bytes
			\|-
			\| BART__FLAGS_URL
			\| 0x02
			\| Contains URL to BART content
			\|-
			\| BART__FLAGS_DATA
			\| 0x04
			\| The opaque field is really data the client knows how to process; these items do not need to be downloaded from BART
			\|-
			\| BART__FLAGS_UNKNOWN
			\| 0x40
			\| Used in OSERVICE__BART_REPLY; BART does not know about this ID, please upload
			\|-
			\| BART__FLAGS_REDIRECT
			\| 0x80
			\| Used in OSERVICE__BART_REPLY; BART says use this ID instead for the matching type
			\|}

	{{Protocols/OSCAR/Foodgroups/BART/SNACs}}		{{Protocols/OSCAR/Foodgroups/BART/SNACs}}