RemoteObject slot's call lock Network

A slot call from a replica is synchronous on the QRemoteObjectHost thread so all network traffic is locked during the slot call. It means that any slot call on a remote object can stop all the RemoteObjet Network traffic (long slot, interlock..) on host and so on all host's client nodes.

Thats seems a problem in design and remove robustness of the RemoteObject Network.

Obviously if the Remoted Object is on the Host thread, that's seems normal. But it seems not possible easily to enableRemote objects from other threads, and however, the call seems to be executed in the host thread, not in objects thread.

The Replica side is already completly asynchronous, probably for network reasons.

A way to asynchronize the slot calls on the host would be greatly appreciated, at least for network performance reasons.

Cordially.