<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>eyalvardi</title>
    <description/>
    <link>https://speakerdeck.com/eyalvardi</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/eyalvardi.rss"/>
    <lastBuildDate>2013-09-06 04:32:59 -0400</lastBuildDate>
    <item>
      <title>ASP.NET Web API</title>
      <description>ASP.NET Web-API is a powerful service framework sitting over Asp.Net MVC and lets the developer enforce a RESTful architectural style. After a brief discussion on how the request and response flow in the WebApi pipeline, we will dig into the main extensibility points and see how flexible is the infrastructure. In particular, we will see scenarios like content negotiation, validation, versioning, hosting outside IIS and few others.</description>
      <media:content url="https://files.speakerdeck.com/presentations/4056c490f8fc013074ba5ef371146242/preview_slide_0.jpg?1936153" type="image/jpeg" medium="image"/>
      <content:encoded>ASP.NET Web-API is a powerful service framework sitting over Asp.Net MVC and lets the developer enforce a RESTful architectural style. After a brief discussion on how the request and response flow in the WebApi pipeline, we will dig into the main extensibility points and see how flexible is the infrastructure. In particular, we will see scenarios like content negotiation, validation, versioning, hosting outside IIS and few others.</content:encoded>
      <pubDate>Fri, 06 Sep 2013 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/eyalvardi/asp-dot-net-web-api</link>
      <guid>https://speakerdeck.com/eyalvardi/asp-dot-net-web-api</guid>
    </item>
  </channel>
</rss>
