Chapter 2 Flashcards

1
Q

Peer-peer architecture

A

No always-on server.
Arbitrary end systems directly communite.
Peers request service from other peers, provide service in return to other peers.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Sockets

A

process ends/receives messages to/from its socket.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Does an IP address of host of which process runs suffice for identifying the process?

A

No. Many processes can be running on the same host.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Indetifier

A

Includes both IP addresses and port numbers associated with process on host.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

An application-layer protocol defines:

A

Types of messages exchanged
Message syntax
Message semantics
Rules
Open protocols
Proprietary protocols.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What transport service does an app need?

A

Data Intergrity
Timing
Throughput
Security

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

TCP Service

A

Reliable transport.
Flow control
Congestion Control
Connection-Oriented
Does not provided timing, minimum throughput guarantee, security .

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

UDP Service

A

Unreliable data transfer
Does not provide TCP services.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Vanilla TCP and UDP sockets

A

No encryption
Cleartext passwords sent into socket traverse Internet in cleartext!

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

TLS

A

Transport Layer Security

Provides encrypted TCP connections
Data integrity
End-Point authentication

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

HTTP

A

Hypertext transfer protocol
Web’s application-layer protocol.
Use TCP

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

HTTP is “stateless” meaning:

A

Server maintains no info about past client requests.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Non-presistent HTTP

A

At most one object sent over TCP connection
Downloading multiple objects requires multiple connections.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Persistent HTTP

A

Multiple objects can be sent over single TCP connection between client and server.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

RTT

A

Time for a small packet to travel from client to server and back.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

HTTP Request Message Types

A

POST
GET
HEAD
PUT

17
Q

HTTP Response Status Codes

A

200 OK
301 Moved Permanently
400 Bad Request
404 Not Found
505 HTTP Version Not Supported

18
Q

Cookies

A

used to maintain some states between transactions.
tracking may be invisible to user.

19
Q

Cookie Components

A

Cookie Header line of HTTP response message
Cookie Header line in next HTTP request messsage
Cookie file kept on user’s host, managed by user’s browser
Back-end database at Web site.

20
Q

First Party Cookies

A

Track user behavior on a given website

21
Q

Third Party Cookies

A

Track user behavior across mutliple websites (without user ever choosing to visit tracker site)

22
Q

Web Caches

A

Satisfy client requests without involving orgin server.

23
Q

Why Web Caching?

A

Reduce response time for client request.
Reduce traffice

24
Q

Browser Caching

A

Don’t send object if broswer has up to date cached version.

25
HTTP/2
Decreased delay in mult-object HTTP requests. Divides objects into frames, schedule frames to mitigate HOL blocking.