Should HttpContext implement IFeatureCollection?

[davidfowl]

Why doesn't it? It would allow users to enumerate features as well. Although Revision would be kinda weird to expose. Some of the properties could be implicit implementation

[Tratcher]

I think a direct implementation would be awkward, like the indexer that takes a type and returns an object. Features are an advanced topic that most users won't ever deal with. Why not just add a IFeatureCollection Features { get; } property? And move Get/SetFeature to extensions on IFeatureCollection.

[davidfowl]

Sounds better.

[Tratcher]

Dropping out of backlog because it involves breaking changes on the abstract base class.

[Tratcher]

This keeps coming up as a useful way to create the structures for calling TestServer.Invoke directly.

[davidfowl]

Ah to avoid going through the HttpClient?

[Tratcher]

Yes. HttpClient is convenient but it can only handle simple scenarios. Katana had a separate API that let you set up the server data structures directly.