Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Either handle SOME/IP as a monolith authority_name or consider how to accommodate N number of mechatronics devices #9

Open
2 tasks
PLeVasseur opened this issue Jul 17, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@PLeVasseur
Copy link
Contributor

PLeVasseur commented Jul 17, 2024

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

Depends on outcome of #18

@PLeVasseur PLeVasseur added the enhancement New feature or request label Jul 17, 2024
@PLeVasseur PLeVasseur added this to the v1.6.0-alpha.4 milestone Jul 17, 2024
@PLeVasseur
Copy link
Contributor Author

Tagging @stevenhartley for visibility.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Backlog
Development

No branches or pull requests

1 participant