Closed tambeau closed 2 years ago
I think we should add the connection string support across all the clients.
Also, we need to explain how to use gossip for connecting, depending on the node preference.
Note: The following server protocols have been added:
Minimum Viable Tier
This is the minimum required to write an application connecting to Event Store. Not all features are available, but the ones that are most commonly used are.
We will support these clients, but users must accept that some features are not going to be available to them.
References:
List of clients supported at this tier:
The Go client is still in early development and should meet the Minimum Viable Tier but may take a tad longer to achieve.
Note: We will need to put in the code for those calls that are to be retired a warning that can be published to the log. This is to remind users that the call is subject to change, temporary in nature and that they will need to be prepared to change it in the near future.
This allows us to warn them of coming change, to use caution and to have a plan for when we do change it ... depreciation warning
Connectivity: Covered by RFC: #574
Streams API: ~This should eventually be defined in the RFC: Home#551~
Persistent Subscriptions API: As defined in RFC: #022
Samples for documentation:
Change log: