pxcloud/spice
6
0
Fork 0
mirror of https://gitlab.uni-freiburg.de/opensourcevdi/spice synced 2026-08-12 19:18:11 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs: Update references to code in spice_threading_model.txt

Browse Source 
Signed-off-by: Frediano Ziglio <freddy77@gmail.com>
Acked-by: Francesco Giudici <fgiudici@redhat.com>
This commit is contained in:
Frediano Ziglio 2020-06-23 22:30:43 +01:00
parent ba065d1bdf
commit 7f849777d3
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/spice_threading_model.txt
View File

@ -35,7 +35,7 @@ One aspect to take into consideration is the event scheduling. SPICE uses some
`SpiceCoreInterface` to handle events. As the events will be handled from a
thread based on the core interface you have to use the correct core. Each
channel has an associated core interface which can be retrieved using
`red_channel_get_core_interface`. There's also a main core interface you can get
`RedChannel::get_core_interface`. There's also a main core interface you can get
using `reds_get_core_interface`. `reds_core_timer_*` and `reds_core_watch_*`
functions use the main core interface.
Even though multiple channel types run in the main thread and so could use
@ -73,8 +73,8 @@ same RedClient are automatically disconnected.
Who owns RedClient? RedClient is released when the MainChannelClient attached
to it is disconnected. In this case a request is scheduled in the main thread
(even if MainChannelClient runs on the main thread too) and
red_client_disconnect is called which calls red_client_destroy which uses
g_object_unref to free the object.
reds_client_disconnect is called which calls RedClient::destroy which uses
RedClient::unref to free the object.
Where is the MainChannelClient freed? On disconnection like other channel
clients, currently before RedClient which will have a dangling pointer.