Rename Http.Core/Http packages

[danroth27]

Currently Microsoft.AspNet.Http.Core depends on Microsoft.AspNet.Http, which seems backwards.

[Tratcher]

Http contains the abstract HttpContext that most apps will reference directly, where Http.Core contains an actual implementation primarily referenced by Hosting. The naming of Http.Core could be better, but I think swapping it with Http would be detrimental to HttpContext.

[danroth27]

How about Http -> Http.Abstractions?

[Tratcher]

I don't recommend it. Just about everything in the pipeline references HttpContext, so it should stay in the top level Http namespace and package for ease of discovery and usage.

[danroth27]

We can argue about the new names, (I'm fine with just renaming Http.Core to something else), but the current names have to change somehow. Everywhere else that I know of in Core is the thing that other stuff depends on, not the other way around. Think .NET Core vs .NET Framework.

[davidfowl]

Http.Impl yay java

[davidfowl]

@danroth27 Did you have any more thoughts on this?

[davidfowl]

We decided to swap the names:

• Http.Core - Abstractions
• Http - Implementations

/cc @glennc @muratg @lodejard

[Tratcher]

Put everything in the Http namespace.

• Http.Core - Abstract base classes, used to implement middleware
• Http - Implementations, only referenced by Hosting & tests