You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If treating SOME/IP network as a monolith, need to:
when making a request into the SOME/IP network need to, in point-to-point case, carefully use the instance id embedded in the ue_id to ensure that we respond to the correct instance
If we need to accommodate N number of mechatronics devices, need to consider how to accomplish this.
Outcome from @stevenhartley talking with folks internally is that we need to support N number of mechatronics devices by both instance_id and different authority_name.
Need to:
Update message_conversion.rs to appropriately handle instance_ids
Handle authority_name on a per-mechatronics-device basis
If treating SOME/IP network as a monolith, need to:
ue_id
to ensure that we respond to the correct instanceIf we need to accommodate N number of mechatronics devices, need to consider how to accomplish this.
Outcome from @stevenhartley talking with folks internally is that we need to support N number of mechatronics devices by both instance_id and different authority_name.
Need to:
Depends on outcome of #18
The text was updated successfully, but these errors were encountered: