tree 1d8f2a005f91b619c93e17543010bc3d86c6cd3e
parent 78fec185c103f3508210812299d8d55823e0bb52
author Boris Zbarsky <bzbarsky@apple.com> 1670440589 -0500
committer GitHub <noreply@github.com> 1670440589 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJjkOaNCRBK7hj4Ov3rIwAAgtgIADnLPe+wnSorQ/fw+n92hQuf
 x5HqquXCZebakSXHKylfWrKC9n3OXZdVgorbyuKGovjQ5NuclL+DFnxyDMHjqvVO
 N3EZmoQa6DB++UDZ/uiX/VhJp+Q95RnOLyXTOuT4EpXkyHsRmCF59bGcWAYVY/1i
 Hu12zSsmdmyX3Ja7mUXX7ccKo31Bj0pDwEdUZzf3K/FEmxMQt4ygUabAhGzGBqoP
 aQzFotRtjr1Cii6mknSz2QLwtDbQgLsOSE1ZBETDRniVDwK/XnezReuEWuenwMDZ
 X3MBfqN864Tqt3dAu892u8UGFwC7m4/p4O4Iq12cVlU2D0rnfpU8vzCBXl5qwBA=
 =v4a1
 -----END PGP SIGNATURE-----
 

Make queue handling consistent for commands in MTRDevice/MTRClusters. (#23959)

invokeCommandWithEndpointID on MTRDevice ran the async work item management
logic on the MTRDevice's work queue, and queued an async callback to the client
queue for the command response.  This was different from what MTRClusters did:
that ran the management logic on the client queue as well.

This PR aligns on the invokeCommandWithEndpointID behavior, because the
MTRClusters behavior allows a poorly-behaved client that blocks inside the
completion handler to completely block the device's async callback queue
processing.