renaming Microsoft.AspNet.HttpFeature to Microsoft.AspNet.HttpFeature.Interfaces

[tugberkugurlu]

I assume that Microsoft.AspNet.HttpFeature library only holds AssemblyNeutral interfaces. In order to align with other similar libraries (like Microsoft.Framework.Logging.Interfaces, Microsoft.Framework.Runtime.Interfaces, etc.), I think it would be better to rename this to Microsoft.AspNet.HttpFeature.Interfaces or something similar.

[Tratcher]

Interesting. The cases aren't quite the same though. Logging.Interfaces is paired with the Logging package just like Runtime.Interfaces is paired with the Runtime package. If we made a HttpFeature.Interfaces package it would have no matching HttpFeature package. Maybe we could pair it with one of the other packages? PipelineCore is where most of the interfaces are consumed.

[tugberkugurlu]

Yes, that could be the case. I am not sure whether .Interfaces thing is a convention but it seems like a good indicator that the library can be used as build dependency in aspnet50 and aspnetcore50 frameworks. There are already libraries using this as a build dependency like Microsoft.AspNet.Owin.

[davidfowl]

Done