Skip to content

Commit

Permalink
Merge pull request #81 from EventStore/rsowald-tcp-deprecation
Browse files Browse the repository at this point in the history
Update README with TCP deprecation notes
  • Loading branch information
thefringeninja committed Mar 11, 2024
2 parents a673f2c + db87e3e commit 0b3a852
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,9 @@

EventStoreDB is the open-source, functional database with Complex Event Processing in JavaScript.

This is the repository for the legacy .NET TCP client for EventStoreDB version 5+ and uses TCP as the communication protocol.
If you're looking for the new recommended .NET gRPC client, check the [EventStore-Client-Dotnet](https://github.com/EventStore/EventStore-Client-Dotnet) repo.
This is the repository for the legacy .NET TCP client for EventStoreDB version 5 - 23.10 and uses TCP as the communication protocol. ESDB versions later than 23.10 do not support TCP.

For the preferred .NET gRPC client, visit the [EventStore-Client-Dotnet](https://github.com/EventStore/EventStore-Client-Dotnet) repository.

## Support

Expand All @@ -28,13 +29,13 @@ Then create the certificates for the tests in the `certs` directory:

## Documentation

Documentation for EventStoreDB can be found here: [Event Store Docs](https://eventstore.com/docs/).
Documentation for EventStoreDB can be found here: [Event Store Docs](https://developers.eventstore.com/).

## Community

We have a community discussion space at [Event Store Discuss](https://discuss.eventstore.com/). If you prefer slack, there is also an #eventstore channel in the [DDD-CQRS-ES](https://j.mp/ddd-es-cqrs) slack community.
Interact with the Event Store and event sourcing communities on the Event Store [Discuss](https://discuss.eventstore.com/) or [Discord](https://discord.gg/Phn9pmCw3t) forum.

## Contributing

Development is done on the `master` branch.
We attempt to do our best to ensure that the history remains clean and to do so, we generally ask contributors to squash their commits into a set or single logical commit.
To maintain a clean history, we ask contributors to squash their commits into one or a few cohesive commits.

0 comments on commit 0b3a852

Please sign in to comment.