Add Deprecation notice to `encoded connections`

Jarema commented 4 months ago

Overview

As encoded connections are not properly working in many cases, and we always steer users away from them, we should mark them as deprecated in client API and docs.

Clients and Tools

[x] Go @piotrpio - https://github.com/nats-io/nats.go/pull/1674
[x] Java @scottf
[x] JavaScript @aricart
[x] .Net @scottf
[ ] C @levb
[ ] Python @caspervonb
[ ] Ruby @wallyqs
[x] Rust @Jarema
[x] .Net V2 @mtmk

Other Tasks

[ ] docs.nats.io updated @bruth
[ ] Update ADR to Implemented
[ ] Update client features spreadsheet

Client authors please update with your progress. If you open issues in your own repositories as a result of this request, please link them to this one by pasting the issue URL in a comment or main issue description.

aricart commented 4 months ago

JavaScript doesn't implement encoded connections.

Jarema commented 4 months ago

Rust client also does not implement encoded connectionts.

scottf commented 4 months ago

Java does not implement encoded connections. .NET V1 does.

Tochemey commented 2 months ago

Ok please what is the best option for those of us who have been using it. Is there any migration doc?

Jarema commented 2 months ago

@Tochemey We are working on typed pub/sub/kv semantics in clients right now. Until then, manual serialize/deserialize of the payload is the way to go.

artooro commented 2 months ago

@Jarema do you have a link to the issue for the typed pub/sub/kv semantics? I've been using encoded connections for awhile and was surprised to see the deprecated notice after updating the Go package. Curious what these new typed semantics looks like and whether I should wait to get off of encoded conn until typed semantics is ready.

nats-io / nats-architecture-and-design