[DRIVERS-2483] Optimize Handshake Client Metadata Created: 26/Oct/22 Updated: 26/Sep/23 Resolved: 26/Sep/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Handshake |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alex Bevilacqua | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | FY23Q1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Driver Changes: | Needed | ||||||||||||
| Description |
|
One piece of feedback from DRIVERS-2209 (WRITING-11730) was that a number of parts of the handshake specification could be refined to further limit the size of the handshake metadata payload (which is capped at 512 bytes). Specifically we should focus on the contents of the client.platform field and how driver naming happens for wrapping libraries, as well as what should/shouldn't be permitted within the field as a whole. |
| Comments |
| Comment by Alex Bevilacqua [ 21/Sep/23 ] |
|
Closing this out as DRIVERS-2708 supersedes this initiatives |
| Comment by Bernie Hackett [ 26/Oct/22 ] |
|
natalya.furmanova@mongodb.com would like us to standardize how we format client.driver.name. |