OWIN Web API with Linky
Download as PPTX, PDF•1 like•978 views
The document discusses OWIN, which defines a standard interface between .NET web servers and applications to promote decoupling and modular development. Key components of OWIN include the environment and appfunc, alongside middleware and web frameworks that assist in application development. It highlights the importance of achieving REST level 3 and provides resources for further exploration.
OWIN Web API with Linky
- 1. OWIN AND WEB API 2.2 Oslo/NNUG Tomas Jansson 26/08/2014
- 2. THIS IS ME Tomas Jansson Manager & Practice Lead .NET BEKK Oslo @TomasJansson [email protected] github.com/mastoj blog.tomasjansson.com
- 3. AGENDA What is OWIN Show me MORE CODE! Terminology Show me the code! RESTWeb API 2.2
- 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
- 18. WEB API 2.2 Full OWIN support Attribute routing Global error handling Multiple OData improvements
- 20. REST/RICHARDSON’S MATURITY MODEL This is our goal today! http://martinfowler.com/articles/images/richardsonMaturityModel/overview.png
- 22. Summary Time to pick up OWIN Key components of OWIN: Environment and AppFunc REST level 3 is doable!
- 23. RESOURCES OWIN: http://owin.org/ Katana: https://katanaproject.codeplex.com/ Presentation: http://www.slideshare.net/mastoj/owin-web-api-with-linky Source code: https://github.com/mastoj/OwinLinkyApi Linky: https://github.com/zudio/Linky
- 24. Questions?