| 2014-06-10 01:42:23 |
Dmitry Kiselev |
description |
The general expectation (correct me, if not, please) is that if the xio_disconnect is called twice, there is no hang and the second call just returns with an error (or even without).
If that's not the case, then we have to maintain a more complex state machine duplicating the Accelio states on the caller's side.
On a side note, if I call xio_connection_destroy twice, I get a crash (Signal 11).
All that is on a Linux platform.
Best regards,
Dmitry |
The general expectation (correct me, if not, please) is that if the xio_disconnect is called twice, there is no hang and the second call just returns with an error (or even without).
If that's not the case, then we have to maintain a more complex state machine duplicating the Accelio states on the caller's side.
That is specifically important for a synchronous usage pattern, where the event loops are not spinned permanently and we have to save the statuses.
On a side note, if I call xio_connection_destroy twice, I get a crash (Signal 11).
All that is on a Linux platform.
Best regards,
Dmitry |
|
