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
Topics are currently scoped globally, meaning that a name collision occurs between the topics joined by the PubSub capability and the cluster namespace. For example, calling n.PubSub().Join("foo") against a node started via ww start -ns foo will return pubsub.capnp:Topic.publish: topic already exists.
To remedy this, we should add the cluster namespace to each topic as a dot-separated prefix. Thus, Join("foo") from our previous example would produce the fully-qualified topic foo.foo.
Interestingly, we might use this mechanism to support an empty "" that is nonetheless distinct from the cluster topic (it would map to the topic .).
The text was updated successfully, but these errors were encountered:
Topics are currently scoped globally, meaning that a name collision occurs between the topics joined by the
PubSub
capability and the cluster namespace. For example, callingn.PubSub().Join("foo")
against a node started viaww start -ns foo
will returnpubsub.capnp:Topic.publish: topic already exists
.To remedy this, we should add the cluster namespace to each topic as a dot-separated prefix. Thus,
Join("foo")
from our previous example would produce the fully-qualified topicfoo.foo
.Interestingly, we might use this mechanism to support an empty
""
that is nonetheless distinct from the cluster topic (it would map to the topic.
).The text was updated successfully, but these errors were encountered: