Repository navigation
.NET: Hosted session harness: preserve composite identifier boundaries #8251
Description
Summary
Harden hosted session harness key construction so identifier components remain distinct.
Affected areas
- Python Invocations hosting and its standalone example.
- .NET Foundry hosting in-memory session store.
Expected behavior
Distinct identifier combinations select independent sessions; repeated requests for the same combination retain continuity. Existing local-mode behavior remains unchanged.
Plan
Use an unambiguous JSON string key for Python Invocations and a typed composite key for the .NET in-memory store. Add focused regression coverage and run the affected suites. No Responses hosting redesign or public API additions.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
[-]Hosted session harness: preserve composite identifier boundaries[/-][+]Python: Hosted session harness: preserve composite identifier boundaries[/+][-]Hosted session harness: preserve composite identifier boundaries[/-][+].NET: Hosted session harness: preserve composite identifier boundaries[/+]Ricky-7-Yan commentedon Sep 10, 2026
I'd like to take this on. I'll keep the change scoped to the Python Invocations and .NET Foundry hosting in-memory stores described here, add collision/continuity regression coverage for both, and preserve local-mode behavior.
test(hosting): extend session key harness
perf(hosting): reuse composite session keys
docs(hosting): keep composite session IDs opaque
chore(hosting): merge main session store changes
.NET: Preserve hosted session key boundaries (microsoft#8263)