zenoh unifies data in motion, data in-use, data at rest and computations. It carefully blends traditional pub/sub with geo-distributed storages, queries and computations, while retaining a level of time and space efficiency that is well beyond any of the mainstream stacks.
There is no current way to have a EntityGlobalId corresponding to a Session, so it's not possible to have a SourceInfo corresponding to a Session.
As discussed with @OlivierHecart, Session should have an EntityId, which may be 0, or not in the case of multiple session sharing a same runtime (e.g. plugins).
Also, according to @OlivierHecart, we may want Reply::replier_id to be an EntityGlobalId instead of a ZenohId.
Describe the release item
There is no current way to have a
EntityGlobalId
corresponding to aSession
, so it's not possible to have aSourceInfo
corresponding to aSession
. As discussed with @OlivierHecart,Session
should have anEntityId
, which may be 0, or not in the case of multiple session sharing a same runtime (e.g. plugins).Also, according to @OlivierHecart, we may want
Reply::replier_id
to be anEntityGlobalId
instead of aZenohId
.@Mallets @milyin What do you think?