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

Document design for transport::UTransport #115

Open
gregmedd opened this issue May 21, 2024 · 1 comment
Open

Document design for transport::UTransport #115

gregmedd opened this issue May 21, 2024 · 1 comment
Milestone

Comments

@gregmedd
Copy link
Contributor

gregmedd commented May 21, 2024

The base UTransport object is, in theory, pretty simple. The bulk of the work will be in the individual transport implementations (e.g. ZenohUTransport). However, it is possible that UTransport might need to do a little more than just pass calls through to its virtual interfaces. This design should consider:

  • If UTransport needs a thread pool for callbacks (so the transport implementations don't have to do it)
  • If UTransport should do anything to prevent multiple parallel calls to the same callback (so callbacks don't have to add extra thread safety concerns)
  • If there are any threads, how do they get shut down?
  • (possibly other things?)
@gregmedd gregmedd added this to the alpha.2 milestone May 21, 2024
@cbeck83
Copy link

cbeck83 commented May 22, 2024

Recommend Uzi for this one

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Backlog
Development

No branches or pull requests

2 participants