MIS365 9 - Internet Protocols - General Architecture

MIS365 9 - Internet Protocols - General Architecture -...

Info iconThis preview shows pages 1–11. Sign up to view the full content.

View Full Document Right Arrow Icon
MIS365 Jerry Malcolm Internet Protocols – General Architecture
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Internet Communications Two basic design points of internet communications: Request / Response Stateless
Background image of page 2
Internet Communications Request / Response The client sends a request The server sends a response The response can often generate a second request Not supported: “Give me some info now and some more later”
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Internet Communications Stateless At the basic TCPIP level The server has no memory of the request The server does not track ‘sessions’ A request is received The request is serviced A second request is received It’s a new sunrise…
Background image of page 4
Internet Communications How does this correlate with web sessions? Once I log in, the server knows me It tracks my shopping cart, etc.
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Web Sessions “Web Sessions” are an artificial abstraction Added on top of the TCPIP protocol Server generates a ‘session key’ Typically just a long string of characters Session key is returned with first response to the client Browser sends the key back in on subsequent requests Server will use the session key to remember what it chooses
Background image of page 6
Web Sessions Are there problems that need to be addressed with sessions? eBay does not have “one server” They have a huge server farm A ‘ sprayer ’ server sits in front of the farm and routes requests Each request will likely go to a different server based on load balancing of the server farm (We’ll discuss clustering in a couple of weeks…) Server 1 generated and sent a key back on a response Next request from the client (with the key) comes to Server 2 Server 2 does not recognize the key
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Web Sessions Two possible solutions 1) The sprayer needs to send all requests from a particular IP address to the same server 2) Servers need to store session information in a common database Slow performance
Background image of page 8
Multiple Concurrent Requests When a request is sent, there is an understandable wait time for the response Wait time can vary But it won’t go to zero We need to be able to send out multiple concurrent requests Much more efficient Even to the same server “Fill up all the pipes”… minimize dead time
Background image of page 9

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Multiple Concurrent Requests Web page example
Background image of page 10
Image of page 11
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/20/2011 for the course MIS 365 taught by Professor Malcolm during the Spring '09 term at University of Texas.

Page1 / 35

MIS365 9 - Internet Protocols - General Architecture -...

This preview shows document pages 1 - 11. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online