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

Add the table for listeners to distinguish different message types. #188

Merged
merged 5 commits into from
Jul 17, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions up-l1/zenoh.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -129,3 +129,39 @@ Take some examples:
| Receive all Requests | //+++*+++/FFFF/FF/FFFF | //my-host2/20EF/4/B | up/+++*+++/+++*+++/+++*+++/+++*+++/my-host2/20EF/4/B
| Receive all messages to a device | //+++*+++/FFFF/FF/FFFF | //[::1]/FFFF/FF/FFFF | up/+++*+++/+++*+++/+++*+++/+++*+++/[::1]/+++*+++/+++*+++/+++*+++
|===

=== Listeners for different message types

Zenoh has different implementations for different uProtocol Message types.
If we register the listeners, we need distinguish the message types and run the corresponding Zenoh mechanisms.
It's important to distinguish the message types based on the various combination of source `resource_id` and sink `resource_id`.

Here is the table:

[%autowidth]
|===
| src resource_id | sink resource_id | Publish | Notification | Request | Response

| [8000-FFFF) | None | V | | |
| [8000-FFFF) | 0 | | V | |
| 0 | (0-8000) | | | V |
| (0-8000) | 0 | | | | V
| FFFF | 0 | | V | | V
| FFFF | (0-8000) | | | V |
| 0 | FFFF | | | V |
| (0-8000) | FFFF | | | | V
| [8000-FFFF) | FFFF | | V | |
evshary marked this conversation as resolved.
Show resolved Hide resolved
| FFFF | FFFF | | V | V | V
|===

These can be reorganized as:

[%autowidth]
|===
| Message Type | Possible resource_id combinations {src_resource_id, sink_resource_id}

| Publish | {[8000-FFFF), None}
| Notification | {[8000-FFFF), 0}, {[8000-FFFF), FFFF]}, {FFFF, 0}, {FFFF, FFFF}
| Request | {0, (0-8000)}, {0, FFFF}, {FFFF, (0-8000)}, {FFFF, FFFF}
| Response | {(0-8000), 0}, {(0-8000), FFFF}, (FFFF, 0), {FFFF, FFFF}
|===
evshary marked this conversation as resolved.
Show resolved Hide resolved