Skip to content

Conversation

@acogoluegnes
Copy link
Collaborator

The client/server terminology can be confusing considering both are client applications and RabbitMQ is still the server (broker).

We also remove the usage of RPC in favor of request/response. See https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901252.

The client/server terminology can be confusing considering both are
client applications and RabbitMQ is still the server (broker).

We also remove the usage of RPC in favor of request/response.
See https://docs.oasis-open.org/mqtt/mqtt/v5.0/os/mqtt-v5.0-os.html#_Toc3901252.
@acogoluegnes acogoluegnes added this to the 0.8.0 milestone Sep 11, 2025
@acogoluegnes acogoluegnes added refactoring Internal refactoring usability breaking-change and removed refactoring Internal refactoring labels Sep 11, 2025
@acogoluegnes acogoluegnes merged commit 0bd8e91 into main Sep 11, 2025
1 check passed
@acogoluegnes acogoluegnes deleted the rename-rpc-to-request-response branch September 11, 2025 10:03
github-actions bot pushed a commit that referenced this pull request Sep 11, 2025
Rename RpcClient/RpcServer to Requester/Responder
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants