Professional Documents
Culture Documents
Cookies, FTP,
Electronic Mail & DNS
2
User-server state: cookies
many Web sites use cookies example:
Susan always access Internet
four components:
from PC
1) cookie header line of
visits specific e-commerce
HTTP response
site for first time
message
when initial HTTP requests
2) cookie header line in arrives at site, site creates:
next HTTP request
message unique ID
entry in backend
3) cookie file kept on
database for ID
user’s host, managed
by user’s browser
4) back-end database at
Web site
Application Layer 2-3
Cookies: keeping “state” (cont.)
client server
ebay 8734
usual http request msg Amazon server
cookie file creates ID
usual http response
1678 for user create backend
ebay 8734
set-cookie: 1678 entry database
amazon 1678
usual http request msg
cookie: 1678 cookie- access
specific
usual http response msg action
9
FTP: the file transfer protocol
file transfer
FTP FTP FTP
user client server
interface
user
at host remote file
local file system
system
13
Electronic mail outgoing
message queue
user mailbox
Three major components: user
user agents agent
24
DNS: domain name system
people: many identifiers: Domain Name System:
SSN, name, passport # distributed database
Internet hosts, routers: implemented in hierarchy of
IP address (32 bit) - many name servers
used for addressing application-layer protocol: hosts,
datagrams name servers communicate to
“name”, e.g., resolve names (address/name
www.yahoo.com - translation)
used by humans note: core Internet function,
Q: how to map between IP implemented as application-
layer protocol
address and name, and
vice versa ? complexity at network’s
“edge”
… …
gaia.cs.umass.edu
gaia.cs.umass.edu
type=A type=CNAME
name is hostname name is alias name for some
value is IP address “canonical” (the real) name
type=NS www.ibm.com is really
name is domain (e.g., servereast.backup2.ibm.com
foo.com) value is canonical name
value is hostname of
authoritative name type=MX
server for this domain value is name of mailserver
associated with name