How to ensure that the emitTo function reliably passes events?

[Think-M]

Hi Tauri team! ; )

I'm using emitTo for window-specific event communication and want to ensure reliable delivery. From the documentation and my testing, I understand these scenarios might cause events to be missed:

1. Target window not ready
2. No proper listener registered
3. Incorrect emitTo usage
4. Window destroyed prematurely
   Are there any other edge cases or scenarios that could prevent event delivery that I should be aware of?

Additionally, could you share:

1. Recommended patterns to guarantee event delivery in critical workflows?
2. Any plans to implement an acknowledgement mechanism (where senders receive confirmation of event receipt) in future releases?

Looking forward to your insights!

[Think-M]

Hello?
To put it simply, I would like to know:

1. Is it still possible for emitTo messages to fail to reach the target window even when it is working properly?
2. Do I need to implement a response and resend mechanism to ensure successful message delivery?

If the answers are all yes, it's a bit sad. I think it's tedious and requires a lot of code to create a response and resend mechanism for each communication command.

Looking at other frameworks such as Winform and Qt, communication between windows can directly manipulate variables, functions, and so on of the other window, which is simple and reliable.

Is it possible to support inter window communication with reliable responses? (The existing one-way communication between windows can still be retained for communication that requires speed but allows for loss.)