See also similar internal item referred to as RICPLT-2869. We might classify routes in different categories so as to reduce the number of entities that need to reply "ok" before we can continue with a subscription. E.g. if only E2T instances need to confirm subscription routes, then we could have routing manager send requests to E2T instances first and send a confirmation to subscription manager once these have sent their reply. Though it might get to complicated. In the long run, though, we might also do some kind of route checking on receiving a message, whcih would mean subscrption routes must also be updated on xApp side. So maybe not worth thinking about. Need to think how tehse changes affect the interface that subscription manager uses with routing manager. |