opened
danroth27
username_0
Currently Microsoft.AspNet.Http.Core depends on Microsoft.AspNet.Http, which seems backwards.
Http should depend on HttpCore, not the other way around
issue
created
Tratcher
username_1
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.
comment
created
danroth27
username_0
OK - I think we just need to come up with a better name for Http.Core. How about Http.Abstractions?
comment
created
danroth27
username_0
How about Http -> Http.Abstractions?
comment
created
Tratcher
username_1
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.
comment
created
danroth27
username_0
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.
comment
created
davidfowl
username_2
Http.Impl yay java
comment
created
davidfowl
username_2
@username_0 Did you have any more thoughts on this?
comment
created
davidfowl
username_2
We decided to swap the names:

- Http.Core - Abstractions
- Http - Implementations

/cc @glennc @muratg @lodejard
comment
created
Tratcher
username_1
Put everything in the Http namespace.
- Http.Core - Abstract base classes, used to implement middleware
- Http - Implementations, only referenced by Hosting & tests
comment
closed
Tratcher
username_1
issue