Followup: we should probably think about what to do if the new thing has a different NOC than the old thing (e.g. changed CATs)... Right now we will just ignore that and keep using the old NOC.

[anush-apple]

          Followup: we should probably think about what to do if the new thing has a different NOC than the old thing (e.g. changed CATs)...  Right now we will just ignore that and keep using the old NOC.

Similar for the various delegates that can get passed in via MTRDeviceControllerParameters. If they all match what we had before, this is fine, but if not, I think the caller can get into a pretty weird state where notifications are not being delivered where they expect them to be.

Longer-term: can we "swap" which object is being targeted by the XPC channel? If we can, it might be better to take down the old controller, bring up the new controller, and re-target what object XPC will hit....

Originally posted by @bzbarsky-apple in #35148 (comment)

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Remove stale label or comment or this will be closed in 30 days.