Question: In the wayland protocol xml spec, the bind request is described as containing uint name, and a new_id id.
In practice, clients seem to universally provide the entire interface spec instead of the uint name - I've found one third party reference that indicates this happens because the version of such interfaces would be ambiguous.
My question is: where is this (actual) behaviour specified?
Sarah Jamie Lewis /
npub14m…vp58n
2024-08-17 22:08:26
Author Public Key
npub14mfj9wu5ujvu6rxj8w62dvkvqj7myqc6kz0upz3kuw3wx4dz9vgstvp58nPublished at
2024-08-17 22:08:26Event JSON
{
"id": "5340d2e3e48e5608c95a5105db6b379e14a27c6286f9bc3fbbcb38f32279149e",
"pubkey": "aed322bb94e499cd0cd23bb4a6b2cc04bdb2031ab09fc08a36e3a2e355a22b11",
"created_at": 1723932506,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.social/users/sarahjamielewis/statuses/112979640777103107",
"activitypub"
]
],
"content": "Question: In the wayland protocol xml spec, the bind request is described as containing uint name, and a new_id id.\n\nIn practice, clients seem to universally provide the entire interface spec instead of the uint name - I've found one third party reference that indicates this happens because the version of such interfaces would be ambiguous.\n\nMy question is: where is this (actual) behaviour specified?",
"sig": "fa27d0f75dad9f198fa31097089a8d7950964fd782c5c17558eb7aa0564e3ea578cd0814b8e4f9f56d45ee6448418fe810ac3411018eef315c5ca351deef7128"
}