Skip to content

Strict 1 to 1 communication in polling mode #594

@Discolai

Description

@Discolai

We have been using the "listening service model" for a while. And we want to try out “polling service mode” mode, but we found a concerning scenario regarding request routing during our testing.

Given a client runtime which has only trusted fingerprint "xxx" and a server subscribing to the queue "server-1" with fingerprint "xxx" we would expect the following:

  • A service request to ServiceEndpoint("poll://server-1", "xxx") should be routed to the server subscribing to “server-1”.
  • A service request to ServiceEndpoint("poll://server-1", "yyy") should fail.

However, both scenarios end up routing to the server subscribing to “server-1”. Is this intentional to allow a “competing consumers” pattern or is it a bug?

If it is intentional do you have a suggestion to how we can achieve a strict and secure 1 to 1 communication in polling mode?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions