On Thu Oct 9 16:57:52 2025 +0000, Matteo Bruni wrote:
`async_complete_cancel()` is currently called from `async_set_result()`, which is in the server and a step that all asyncs always go through. It doesn't look like moving the whole async "result" handling to the client is something that can be reasonably done in the short term, so I guess my question is whether it seems better to "clarify" that the wait is effectively server-side only by using `server_wait_for_object()` or to return to `NtWaitForSingleObject()` even though that effectively always involves the server. Maybe there are still advantages to allowing in-proc sync even in this case? I'm going to finish setting up ntsync and tinker a bit with it...
Okay, switched back to `NtWaitForSingleObject()`, it was informative (and nice!) to see ntsync in action :smile: