On Wed Oct 8 13:25:51 2025 +0000, Matteo Bruni wrote:
Right, I was wondering if I should create the sync object with `create_server_internal_sync()` instead. The sync is always signaled from the server anyway (`signal_sync()` in `async_complete_cancel()`). BTW, is that an okay way to do it?
Yes, you could create it with `create_server_internal_sync` and then use `server_wait_for_object`, but there's no reason to do that here.
It's mostly only still useful for the couple of object types for which signal / satisfied logic is complicated (completion waits, asyncs), or which require specific handling of the subsequent wait (debug objects, which need to send/receive thread contexts). And I think we should instead work toward getting rid of those requirements and have everything able to use inproc syncs instead.
Here, the sync is already an event-like sync with a simple signaled state, and it can use an inproc sync to save all the extra requests that would be required for the wait operation, and make the wait happen entirely on the client-side / in kernel.