hs-proxy: Keep track of clientCtx and client when starting application 36/25136/1 9.99.4 jellyfish/9.99.4 jellyfish_9.99.4
authorMarius Vlad <marius.vlad@collabora.com>
Wed, 19 Aug 2020 10:11:19 +0000 (13:11 +0300)
committerMarius Vlad <marius.vlad@collabora.com>
Wed, 19 Aug 2020 14:00:07 +0000 (17:00 +0300)
commite5c9cb71a537b92096f2f05058522b811f735838
treef16b8c0fe4c9b77ef9dc0b2880c3849571ed3131
parentf6c6f42502ba2919f23f553239dd8b117440b365
hs-proxy: Keep track of clientCtx and client when starting application

The subscribe verb was used in the past to keep track of applications,
which was done in background with the help of event handlers. As
that no longer happens we keep track of the client and its clientCtx
when starting directly from the homescreen binding, faking the subscribe
logic.

As the afb_req_t object is no longer in scope when the async callback
handler returns, we do it before doing the call to af-main, and assume
that we'll succeed.

We use the async callback handler to  verify if the application was
indeed started but any application crashing afterwards will require an
additional check performed, as it will found in the hash table of
clients.

Bug-AGL: SPEC-3524

Signed-off-by: Marius Vlad <marius.vlad@collabora.com>
Change-Id: I0e417dc5f2953947cd27ca551c0d2a2af5c57e6d
src/hs-clientmanager.cpp
src/hs-proxy.cpp