diff options
| author | wm4 <wm4@nowhere> | 2018-05-10 12:41:01 +0200 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2018-05-24 19:56:34 +0200 |
| commit | 005d3bc81a86dddf458c0d19142815687a303877 (patch) | |
| tree | cbda4116d6e54ccfccda5d0d739762d7a4d36ba6 /DOCS/client-api-changes.rst | |
| parent | 95c4f0f7698879f28cec7159f03fc7fd211bcff7 (diff) | |
| download | mpv-005d3bc81a86dddf458c0d19142815687a303877.tar.bz2 mpv-005d3bc81a86dddf458c0d19142815687a303877.tar.xz | |
client API: clarify asynchronous call ordering non-guarantees
Both asynchronous and synchronous calls used to be put into the core's
dispatch queue. Also, asynchronous calls were actually synchronous, just
without forcing a wait on the client's thread. This meant that both
kinds of calls were always strictly ordered.
A longer time ago, synchronous calls were changed to simply lock the
core. This could possibly lead to reordering. Recently, some commands
were changed to run on worker threads, which made the order even looser.
Also remove another now incorrect doxygen comment regarding async
commands.
Diffstat (limited to 'DOCS/client-api-changes.rst')
0 files changed, 0 insertions, 0 deletions