The combination of resource ID of source and sink

[evshary]

When I'm using the L2 API, I found that InMemoryRpcServer call register_listener with source UUri UUri::any(), which means //*/FFFF/FF/FFFF.

up-rust/src/communication/in_memory_rpc_server.rs

Line 232 in 8a9fe59

origin_filter.unwrap_or(&UUri::any()),

I created a table here before to list all the combinations of resource ID for register_listener.

The reason I removed source resource_id=FFFF & sink resource_id=[1-7FFF] is that the source resource_id should always be 0 here. However, I agree that in the L2 API case, it might be annoying for users to use //*/FFFF/FF/0 as the source Uri.

Furthermore, if we decided to add back the combination of {FFFF, 1-7FFF}, then it will come across the question I met before. Should we also add back the other cases?

@sophokles73 WDYT?

[sophokles73]

I agree that in line 232 we should use //*/FFFF/FF/0 as the origin filter if not specified explicitly by the user.

[sophokles73]

Would you like to create a PR?