From port 80 to applications


Published on

In this presentation I try to help developers understand all that goes in to the full web request life cycle. From the client to the server and what and where things happen.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Demo in IE & Chrome
  • The following list describes the request-processing flow:When a client browser initiates an HTTP request for a resource on the Web server, HTTP.sys intercepts the request.HTTP.sys contacts WAS to obtain information from the configuration store.WAS requests configuration information from the configuration store, applicationHost.config.The WWW Service receives configuration information, such as application pool and site configuration.The WWW Service uses the configuration information to configure HTTP.sys.WAS starts a worker process for the application pool to which the request was made.The worker process processes the request and returns a response to HTTP.sys.The client receives a response.
  • MVC was first described in 1979[2] by TrygveReenskaug, then working on Smalltalk at Xerox PARC. The original implementation is described in depth in the influential paper "Applications Programming in Smalltalk-80: How to use Model–View–Controller".[3]- From wikipedia (
  • All
  • From port 80 to applications

    1. 1. From Port 80 to Applications<br />@woodyp<br /><br /><br />
    2. 2. Agenda<br />Why do you want to be here?<br />Where did the web come from?<br />What parts are there to the web?<br />What is a web server?<br />What is a web browser?<br />How can we control the experience?<br />What dose ASP.NET do?<br />Why are there web forms and MVC?<br />What more should you know?<br />
    3. 3. This session is about you!<br />
    4. 4. How did we get here?<br />Opte Project<br /><br />
    5. 5. Overview Time Line<br />1960’s<br />Electronic mail<br />1962 when the RAND tackled the problem of how they could communicate in the aftermath of a nuclear attack<br />1969<br />Telnet: A system for logging in, over a network, to a computer situated in another location.<br />ARPANET connected Stanford research Institute in Santa Barbara to the University of Utah<br />…<br />Source: & <br />
    6. 6. Overview<br />Packet-switched networking<br />ARPANET<br />Telenet<br />X.25<br /> Internet Protocol Suite<br />TCP/IP<br />
    7. 7. How dose it work?<br />IPv6 used to identify and locate hosts on the network<br />Transport Layer handles direct host-to-host communication tasks<br />Which provides a general framework to transmit data between hosts using protocols like the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP).<br />
    8. 8. Or Better Said<br />Source:<br />
    9. 9. And<br />Source:<br />
    10. 10. Internet Protocol Suite<br />Application Layer<br />BGP · DHCP · DNS · FTP · HTTP · IMAP · IRC · LDAP · MGCP · NNTP · NTP · POP · RIP · RPC · RTP · SIP · SMTP · SNMP · SSH · Telnet · TLS/SSL · XMPP · (more)<br />Transport Layer<br />TCP · UDP · DCCP · SCTP · RSVP · ECN ·(more)<br />Internet Layer<br />IP (IPv4, IPv6) · ICMP · ICMPv6 · IGMP · IPsec · (More)<br />Link Layer<br />ARP/InARP · NDP · OSPF · Tunnels (L2TP) · PPP · Media Access Control (Ethernet, DSL, ISDN, FDDI) · (more).<br />
    11. 11. Where web devs live<br />Hypertext Transfer Protocol (HTTP)<br />June 1999 RFC 2616 (defines HTTP/1.1)<br />At First the only supported method was GET<br />The response from the server was always an HTML page<br />By March 1996, pre-standard HTTP/1.1 was supported in<br />Arena, Netscape 2.0, Netscape Navigator Gold 2.01, Mosaic 2.7, Lynx 2.5, and in Internet Explorer 3.0. link<br />
    12. 12. HTTP Methods<br />HEAD<br />Like GET request, but without the response body.<br />GET<br />Requests a representation of the specified resource. <br />POST<br />Submits data to be processed<br />PUT<br />Uploads a representation of the specified resource.<br />
    13. 13. HTTP Methods<br />DELETE<br />Deletes the specified resource.<br />TRACE<br />Echoes back the received request<br />OPTIONS<br />Returns the HTTP methods that the server supports for specified URL<br />CONNECT<br />Converts the request connection to a transparent TCP/IP tunnel<br />PATCH<br />Is used to apply partial modifications to a resource.<br />
    14. 14. Request Life Cycle<br />Client Request (URL)<br /><br /><br /><br />Response to client<br />Request Routing<br />Name Server resolves ULR with Domain name system (DNS)<br />Server Processes<br />
    15. 15. Where is the Magic?<br />
    16. 16. Web Servers<br />Receive Request<br />Process Request<br />ISAPI (Internet Server Application Programming Interface)<br />CGI (Common Gateway Interface)<br />IIS 7 (Managed Code or Unmanaged Code)<br />Return Requested Resource<br />Or Error if not available<br />
    17. 17. IIS 7<br />
    18. 18. IIS Cycle<br />
    19. 19. Process RequestFor IIS 7 & ASP.NET<br />
    20. 20. ASP.NET Page<br />
    21. 21. ASP.NET MVC<br />
    22. 22. DEMO<br />
    23. 23. Resources <br />Internet History<br /><br /><br /><br />Tools<br /><br /><br /><br />
    24. 24. Thank You<br />Woody PewittTechnical EvangelistDevExpress<br />@woodyp<br /><br /><br />