{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

lec-7 - What's next Network Applications P2P File Sharing...

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

View Full Document Right Arrow Icon
19 Aug 2008  BITS C481 (Computer Networks) 1 What’s next… Network Applications P2P File Sharing Techniques Web and HTTP
Background image of page 1

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

View Full Document Right Arrow Icon
19 Aug 2008  BITS C481 (Computer Networks) 2 P2P: Centralized Directory Original “Napster” design 1) When peer connects, it informs central server: IP address Content 2) Alice queries for “Hey Jude” 3) Alice requests file from Bob centralized directory server peers Alice Bob 1 1 1 1 2 3 Problems: Single point of failure Performance bottleneck Copyright infringement File transfer is decentralized, but locating content is highly centralized!!!
Background image of page 2
19 Aug 2008  BITS C481 (Computer Networks) 3 Query flooding: Gnutella Fully distributed No central server Public domain protocol Many Gnutella clients implementing protocol Overlay Network: graph Edge between peer X and Y if there’s a TCP connection All active peers and edges is overlay network Edge is not a physical link Given peer will typically be connected with < 10 overlay neighbors
Background image of page 3

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

View Full Document Right Arrow Icon
19 Aug 2008  BITS C481 (Computer Networks) 4 Gnutella: protocol Query QueryHit Query Query QueryHit Query Query QueryHit File transfer: HTTP Query message sent over existing TCP connections Peers forward Query message Query Hit sent over reverse path Scalability: limited scope flooding
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.
  • Fall '08
  • Prof.VirendraSinghShekhawat
  • World Wide Web, Web server, group leader, Aug, Hypertext Transfer Protocol, TCP connection

{[ snackBarMessage ]}