RFC-0047: Unified User Agent #141
Conversation
| | ------------- | ---------- | | ||
| | .NET | `dotnet` | | ||
| | C++ | `cxx` | | ||
| | Go | `golang` | |
There was a problem hiding this comment.
@chvck Should we split this to gocb and gocbcore which more closely aligns with what gocb/gocbcore currently do?
There was a problem hiding this comment.
| | Go | `golang` | | |
| | Go | `gocb` | | |
| | Go Core | `gocbcore` | |
| | Scala | `scala` | | ||
| | Kafka | `kafka` | | ||
| | ElasticSearch | `es` | | ||
|
|
There was a problem hiding this comment.
| | Java Columnar | `couchbase-java-columnar` | | |
| | Node.js Columnar | `nodejs-columnar` | | |
| | Python Columnar | `python-columnar` | | |
Seems like we might as well add the Columnar SDKs since we are making an update when they are already in existence.
|
I don't have a strong opinion, but just to voice it… Seeing things like "java/3.7.5" in the string seem a bit misleading. It's not really "java". I know not many unfamiliar with Couchbase will be looking at this, but it does make be wonder if a couple more characters like "javacb" or "cbjava" disambiguate it better. There may be some collisions that could be confusing. "python/4.1.3" could collide next year with an actual python runtime. If ya'll think I'm being too pedantic, I'm good to go with the suggestions. Also, regarding "couchbase-java-columnar" (23 chars?), the server side is going to use only up to the first 32 characters or a space, whichever comes first, in statistics aggregation (but not logging). so something like "javacbcol" might be better to avoid a git hash or the like being excluded. |
No description provided.