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
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?)
The text was updated successfully, but these errors were encountered:
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 thatUTransport
might need to do a little more than just pass calls through to its virtual interfaces. This design should consider:UTransport
needs a thread pool for callbacks (so the transport implementations don't have to do it)UTransport
should do anything to prevent multiple parallel calls to the same callback (so callbacks don't have to add extra thread safety concerns)The text was updated successfully, but these errors were encountered: