Move IServerInformation and IServerFactory into a package that server authors can use

[davidfowl]

Today IServerInformation exists in Microsoft.AspNet.Http and IServerFactory exists in Hosting. We need to have a simple package that server authors like Nowin can use to implement the ASP.NET 5 server abstraction.

[davidfowl]

Proposal

Microsoft.AspNet.Hosting.Interfaces - Interfaces made available to applications that use the ASP.NET hosting model.

• IHttpContextAccessor.cs
• IHostingEnvironment.cs
• IApplicationLifetime.cs

In theory, another hosting library could implement these interfaces and most ASP.NET apps would still work.

Microsoft.AspNet.Server.Interfaces - The WebServer contract.

• IServerFactory.cs

Depends on

• Microsoft.Framework.ConfigurationModel.Interfaces
• Microsoft.AspNet.FeatureModel
• Microsoft.AspNet.Http

Some interfaces stay inside of the hosting package itself since they are pretty much implementation details.

Can be overridden by the user but live in the hosting package itself since they are pretty specific to the Microsoft.AspNet.Hosting pipeline:

• IHttpContextFactory.cs
• IApplicationBuilderFactory.cs
• IStartupFilter.cs
• IServerLoader.cs

These interfaces can't be overridden by the application but can be overridden if you're using hosting like a library.

• IHostingEngine.cs
• IStartupLoader.cs

Thoughts? /cc @lodejard @glennc @Eilon @muratg @HaoK

[muratg]

Sounds fine to me. How about IServerInformation?

[muratg]

@davidfowl assuming you wanted this in RC, assigning this to Prabu.

[davidfowl]

Renamed Hosting.Server interfaces to M.A.Server.Interfaces and made some tweaks due to the refactoring that @HaoK and @lodejard came up with.

[HaoK]

Since we already have a .Server subnamespace, maybe it would be clearer if we had a Engine namespace for the engine and the four interfaces that are only used by the HostingEngine, and also roll what currently lives in the Startup/Builder/Internal namespaces into Engine as well?? i.e.

M.A.Hosting.Engine:

• HostingEngine
• IHostingEngine
• IApplicationBuilderFactory
• ApplicationBuilderFactory
• IHttpContextFactory
• HostingContextFactory
• IStartupFilter
• IServerLoader
• IStartupLoader
• StartupLoader
• StartupMethods
• Configure[Services]Delegate
• [Internal namespace] RequestServicesContainer/Middleware + AutoRequestServicesStartupFilter

[davidfowl]

I would move things out of the Engine namespace that can be overridden by the application

[HaoK]

So maybe collapse everything into root Microsoft.AspNet.Hosting except for

IHostingEngine and IStartupLoader which live in Microsoft.AspNet.Hosting.Engine, and the ones you've already called out?

[davidfowl]

Yep