AD: /* ICQ Message Extensions */

2021-02-13T06:35:24Z

ICQ Message Extensions

AD at 06:34, 13 February 2021

2021-02-13T06:34:17Z

← Older revision		Revision as of 06:34, 13 February 2021
Line 693:		Line 693:
	</pre>		</pre>

			== ICQ Message Extensions ==

AD at 01:31, 13 February 2021

2021-02-13T01:31:55Z

Show changes

AD at 01:03, 13 February 2021

2021-02-13T01:03:14Z

Show changes

AD: Created page with "{{Protocols/OSCAR}} OSCAR uses UUIDs in several places to express what kind of capabilities a client has and what features it would like the server to support. The nice thing..."

2020-03-17T03:34:11Z

Created page with "{{Protocols/OSCAR}} OSCAR uses UUIDs in several places to express what kind of capabilities a client has and what features it would like the server to support. The nice thing..."

New page

{{Protocols/OSCAR}}

OSCAR uses UUIDs in several places to express what kind of capabilities a client has and what features it would like the server to support. The nice thing about UUIDs is there does not have to be a central registry since they are unique when created. There are many websites and tools out there that will create a UUID. UUIDs are also sometimes known as GUIDs.

UUIDs are transmitted as 16 bytes of binary data; however in documents they are written down in string form like 09460000-4C7F-11D1-8222-444553540000.

At some point it was decided that full UUIDs were too verbose for common capabilities, so AIM uses both full UUIDs and what are called "short UUIDs" or "Short Caps". A "Short Cap" is really a UUID of the form 0946XXYY-4C7F-11D1-8222-444553540000 where XXYY is the short cap. A client receives short caps if it asserts the short cap capability. If a client does not assert the short caps UUID, it will get most caps in long form. Some APIs only take UUIDs In those cases the long form of a short cap should be sent.

Client and library developers should feel free to create valid new UUIDs, just do not create new "Short Caps". If developers would like to publish their UUIDs and what they mean, we will be happy to document them here.

{| class="wikitable"
! width="217" | Name
! UUID
! Notes
|-
| width="217" | SHORT_CAPS
| 09460000-4C7F-11D1-8222-444553540000
| Client support short caps
|-
| width="217" | SECURE_IM
| 09460001-4C7F-11D1-8222-444553540000
| Client supports SECURE_IM
|-
| width="217" | XHTML_IM
| 09460002-4C7F-11D1-8222-444553540000
| Client supports XHTML profile and ims instead of AOLRTF
|-
| width="217" | RTCVIDEO
| 09460101-4C7F-11D1-8222-444553540000
| Client supports SIP/RTP video
|-
| width="217" | HAS_CAMERA
| 09460102-4C7F-11D1-8222-444553540000
| Client has a camera
|-
| width="217" | HAS_MICROPHONE
| 09460103-4C7F-11D1-8222-444553540000
| Client has a microphone
|-
| width="217" | RTCAUDIO
| 09460104-4C7F-11D1-8222-444553540000
| Client supports RTCAUDIO
|-
| width="217" | HOST_STATUS_TEXT_AWARE
| 0946010A-4C7F-11D1-8222-444553540000
| Client supports new status message features
|-
| width="217" | RTIM
| 0946010B-4C7F-11D1-8222-444553540000
| Client support "see as I type" IMs
|-
| width="217" | SMART_CAPS
| 094601FF-4C7F-11D1-8222-444553540000
| Client only asserts caps for services it is participating in
|-
| width="217" | FILE_TRANSFER
| 09461343-4C7F-11D1-8222-444553540000
| File transfer
|-
| width="217" | DIRECT_ICBM
| 09461345-4C7F-11D1-8222-444553540000
| P2p ims
|-
| width="217" | FILE_SHARING
| 09461348-4C7F-11D1-8222-444553540000
| File sharing
|-
| width="217" | SUPPORT_ICQ
| 0946134D-4C7F-11D1-8222-444553540000
| Client supports talking to ICQ users
|}

[[Category:OSCAR]]
[[Category:Work_In_Progress]]

Protocols/OSCAR/UUIDs - Revision history

AD: /* ICQ Message Extensions */

AD at 06:34, 13 February 2021

AD at 01:31, 13 February 2021

AD at 01:03, 13 February 2021

AD: Created page with "{{Protocols/OSCAR}} OSCAR uses UUIDs in several places to express what kind of capabilities a client has and what features it would like the server to support. The nice thing..."