19 - send_message(invocation, invocation, fds);
20 + try
21 + {
22 + send_message(invocation, invocation, fds);
23 + }
24 + // In general we propagate this exception up to the client
25 + // library so that it may invoke appropriate error callbacks,
26 + // etc...however in the case of disconnect the notify_disconnect
27 + // codepath will take care of this and we need to surpress the
28 + // exception here. (lp:1394873)
29 + catch (...)
30 + {
31 + if (!disconnected.load())
32 + throw;
33 + }
This is not really anything to do with the stated reason for this MP is it?
19 - send_message( invocation, invocation, fds); invocation, invocation, fds); load())
20 + try
21 + {
22 + send_message(
23 + }
24 + // In general we propagate this exception up to the client
25 + // library so that it may invoke appropriate error callbacks,
26 + // etc...however in the case of disconnect the notify_disconnect
27 + // codepath will take care of this and we need to surpress the
28 + // exception here. (lp:1394873)
29 + catch (...)
30 + {
31 + if (!disconnected.
32 + throw;
33 + }
This is not really anything to do with the stated reason for this MP is it?