[PATCH v2 2/3] wineusd.sys: Add new service to update user shared data continuously.

[Paul Gofman]

On 4/24/20 16:29, Rémi Bernon wrote:
>
> And once you have a second thread, then why not a third for some other
> "simple" task, etc. As I understand it, the single thread wineserver
> is a principle which suffers from no exception for the sake of
> simplicity. And that will hold until the moment where there's no other
> way -but I don't see that happening soon.

Can't wineserver just spawn another native wineusd server then, give it
a pipe so wineusd can die from SIGPIPE when main server dies, and let
ntdll request the shm object from the second server? If that second
server dies, everything will crash, just like if wineserver dies, but
the life time of such native process does not depend on the win stuff
within Wine prefix. And will avoid Windows mappings which can be
detectable by applications and annoy some excessively sensitive ones.
That's IMO would avoid some issues.