Not sure if this is supposed to work or I am missing some configuration, but when issuing a call from PC instance (a "turn light on" from the lighting example to be precise) to an Android instance, and this one does not return a response from its lighting server, the timed_out service response is never received by the client, which is blocked forever.
This I tried only in PC-Android connection, since in Android uAALization it is common that an app does not return any service response despite being matched (this can be worked around easily, don't worry). But it made me wonder if timed_out responses are also handled automatically by the service bus even in multi-peer scenarios.
If they are supposed to, I can investigate further, with PC-PC connection.
--
From: this issue has been automatically imported from our old issue tracker
Originally Opened: @Alfiva (2015-07-07 10:53:19)
Not sure if this is supposed to work or I am missing some configuration, but when issuing a call from PC instance (a "turn light on" from the lighting example to be precise) to an Android instance, and this one does not return a response from its lighting server, the timed_out service response is never received by the client, which is blocked forever.
This I tried only in PC-Android connection, since in Android uAALization it is common that an app does not return any service response despite being matched (this can be worked around easily, don't worry). But it made me wonder if timed_out responses are also handled automatically by the service bus even in multi-peer scenarios.
If they are supposed to, I can investigate further, with PC-PC connection.
--
From: this issue has been automatically imported from our old issue tracker