4. WHAT IS OWIN?
OWIN defines a standard interface between .NET web servers
and web applications.
The goal of the OWIN interface is to decouple server and
application, encourage the development of simple modules
for .NET web development, and, by being an open standard,
stimulate the open source ecosystem of .NET web
development tools.
http://owin.org/
5. WHAT IS OWIN?
OWIN defines a standard interface between .NET
web servers and web applications.
The goal of the OWIN interface is to decouple server and
application, encourage the development of simple modules
for .NET web development, and, by being an open standard,
stimulate the open source ecosystem of .NET web
development tools.
http://owin.org/What
OWIN is
6. WHAT IS OWIN?
OWIN defines a standard interface between .NET web servers
and web applications.
The goal of the OWIN interface is to decouple server
and application, encourage the development of
simple modules for .NET web development, and, by
being an open standard, stimulate the open source
ecosystem of .NET web development tools.
http://owin.org/
The goal
8. ACTORS
Host: The process an application and server execute inside of, primarily
responsible for application startup.
Example: Self-host, Nowin, IIS
http://owin.org/spec/owin-1.0.0.html
9. ACTORS
http://owin.org/spec/owin-1.0.0.html
Server: The HTTP server that directly communicates with the client and then
uses OWIN semantics to process requests.
Examples: SystemWeb, Self-Host, Nowin
Host: The process an application and server execute inside of, primarily
responsible for application startup.
Example: Self-host, Nowin, IIS
10. ACTORS
Middleware: A pass through component that handles cross cutting concerns.
Acts as a pipeline between server and application.
Example: Security stuff
http://owin.org/spec/owin-1.0.0.html
Server: The HTTP server that directly communicates with the client and then
uses OWIN semantics to process requests.
Examples: SystemWeb, Self-Host, Nowin
Host: The process an application and server execute inside of, primarily
responsible for application startup.
Example: Self-host, Nowin, IIS
11. ACTORS
Middleware: A pass through component that handles cross cutting concerns.
Acts as a pipeline between server and application.
Example: Security stuff
Web Framework: Self-contained components that you can base your application
on.
Example: Web API, NancyFx, SignalR
http://owin.org/spec/owin-1.0.0.html
Server: The HTTP server that directly communicates with the client and then
uses OWIN semantics to process requests.
Examples: SystemWeb, Self-Host, Nowin
Host: The process an application and server execute inside of, primarily
responsible for application startup.
Example: Self-host, Nowin, IIS
12. ACTORS
Middleware: A pass through component that handles cross cutting concerns.
Acts as a pipeline between server and application.
Example: Security stuff
Web Framework: Self-contained components that you can base your application
on.
Example: Web API, NancyFx, SignalR
Web Application: This is the stuff you’re most likely to write.
http://owin.org/spec/owin-1.0.0.html
Server: The HTTP server that directly communicates with the client and then
uses OWIN semantics to process requests.
Examples: SystemWeb, Self-Host, Nowin
Host: The process an application and server execute inside of, primarily
responsible for application startup.
Example: Self-host, Nowin, IIS
14. ENVIRONMENT
The Environment dictionary stores information about the request,
the response, and any relevant server state.
The server is responsible for providing body streams and header
collections for both the request and response in the initial call.
The application then populates the appropriate fields with response
data, writes the response body, and returns when done.
15. APPFUNC – THE APPLICATION DELEGATE
http://casopisinterfon.org/2014/03/11/da-li-funk-od-balkana-pravi-pesme-ili-balkan-od-funka-pravi-slona/
16. APPFUNC – THE APPLICATION DELEGATE
using AppFunc = Func<IDictionary<string, object>, // Environment
Task>; // Done
17.
18. WEB API 2.2
Full OWIN support
Attribute routing
Global error handling
Multiple OData improvements