protocol: try to clarify frame callback semantics
protocol: try to clarify frame callback semantics

"the callback event will arrive after the next output refresh" is wrong,
if you interpret "output refresh" as framebuffer flip or the moment when
the new pixels turn into light the first time. Weston has probably never
worked this way.

Weston triggers the frame callbacks when it submits repainting commands
to the GPU, which is before the framebuffer flip.

Strike the incorrect claim, and the rest of the paragraph which no
longer offers useful information.

As a replacement, expand on the "throttling and driving animations"
characteristic. The main purpose is to let clients animate at the
display refresh rate, while avoiding drawing frames that will never be
presented.

The new claim is that the server should give some time between
triggering frame callbacks and repainting itself, for clients to draw
and commit. This is somewhat intimate with the repaint scheduling
algorithm a compositor uses, but hopefully the right intention.

Another point of this update is to imply, that frame callbacks should
not be used to count compositor repaint cycles nor monitor refresh
cycles. It has never been guaranteed to work. Removing the mention of
frame callback without an attach hopefully discourages such use.

v2: Don't just remove a paragraph, but add useful information about the
request's intent.

v3: Specify the order of posting frame callbacks.

Signed-off-by: Pekka Paalanen <0f6ae7001e34c37b02fb2c1c2573ddf8f442136a@collabora.co.uk>
Cc: Axel Davy <2b6ef604b998fb81662f85c329e4fc020eae8e5d@ens.fr>
Cc: Jason Ekstrand <68c46a606457643eab92053c1c05574abb26f861@jlekstrand.net>

bitfactor/wayland,bitfactor/wayland,tulcod/wayland,sir-murray/wayland,mchalupa/wayland,bitfactor/wayland,abooij/wayland,abooij/wayland,tulcod/wayland,sir-murray/wayland,tulcod/wayland,eyolfson/wayland,eyolfson/wayland,mchalupa/wayland,mchalupa/wayland,abooij/wayland,eyolfson/wayland,sir-murray/wayland