You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by "michaeljmarshall (via GitHub)" <gi...@apache.org> on 2023/06/09 02:51:45 UTC
[GitHub] [pulsar-site] michaeljmarshall commented on a diff in pull request #407: [improve][doc] Add note on client/broker compatibility
michaeljmarshall commented on code in PR #407:
URL: https://github.com/apache/pulsar-site/pull/407#discussion_r1223779662
##########
docs/client-libraries.md:
##########
@@ -22,6 +22,14 @@ Pulsar supports the following language-agnostic client libraries:
| REST | [User doc](client-libraries-rest.md) | [Bundled](pathname:///release-notes/) | [Bundled](https://github.com/apache/pulsar/tree/master/pulsar-broker) |
| WebSocket | [User doc](client-libraries-websocket.md) | [Standalone](pathname:///release-notes/client-ws) | [Bundled](https://github.com/apache/pulsar/tree/master/pulsar-websocket) |
+:::note
+
+**Client / Broker compatibility**
+
+A design goal of Pulsar is to ensure full compatibility between the same major version clients and brokers, e.g. 2.x clients are compatible with all 2.x brokers, etc.
Review Comment:
Sorry for the delay here @onobc. What do you think about the following?
```suggestion
A design goal of Pulsar is to ensure full compatibility between all versions of the client and the broker. When a client connects to a broker they agree upon a version of the protocol to use. As a result, new features that rely on an updates to the protocol are only available when using both newer clients and newer brokers.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org