[DRIVERS-2157] Clarify whether to add session ID to endSessions command Created: 19/Jun/19 Updated: 31/Mar/22 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | Sessions |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Major - P3 |
| Reporter: | Divjot Arora (Inactive) | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Needed | ||||||||
| Description |
|
The sessions spec does not mention endSessions in the exceptions section (https://github.com/mongodb/specifications/blob/master/source/sessions/driver-sessions.rst#exceptions-to-sending-the-session-id-to-the-server-on-all-commands) so the assumption is that endSessions should be used in a session. However, the command is used in many drivers to end all open sessions when the client is disconnected and creating an implicit session for it would open up another session on the server, so I think it should be included in the exceptions. |
| Comments |
| Comment by Jeremy Mikola [ 01/Jul/19 ] |
|
Cross-referencing this with some previous questions I asked about an lsid attached to a killSessions command. I still think there's value in clarifying this in the spec, but I think the take-away from HELP-9893 was that passing an lsid to the command wasn't a concern. |
| Comment by Ian Whalen (Inactive) [ 01/Jul/19 ] |
|
jmikola to clarify which way to go on this. |