Content Networking: Architecture, Protocols, and PracticeElsevier, 2005. gada 24. marts - 352 lappuses As the Internet has grown, so have the challenges associated with delivering static, streaming, and dynamic content to end-users. This book is unique in that it addresses the topic of content networking exclusively and comprehensively, tracing the evolution from traditional web caching to today's open and vastly more flexible architecture. With this evolutionary approach, the authors emphasize the field's most persistent concepts, principles, and mechanisms--the core information that will help you understand why and how content delivery works today, and apply that knowledge in the future.
|
No grāmatas satura
1.–5. rezultāts no 30.
9. lappuse
... port number is used to direct messages to the correct application running on the server. If no port number is given, the default port of 80 is assumed for HTTP. Finally, the path component of a URL specifies the exact file and the ...
... port number is used to direct messages to the correct application running on the server. If no port number is given, the default port of 80 is assumed for HTTP. Finally, the path component of a URL specifies the exact file and the ...
17. lappuse
... port number), as TCP represents Layer 4 in the TCP/IP protocol stack. Content switching will be discussed in detail in Chapter 5. Deployment and growth of server farms normally go hand-in-hand with appropriate upgrades of the network ...
... port number), as TCP represents Layer 4 in the TCP/IP protocol stack. Content switching will be discussed in detail in Chapter 5. Deployment and growth of server farms normally go hand-in-hand with appropriate upgrades of the network ...
20. lappuse
... port numbers are frequently used for drawing conclusions on the encapsulated application data. TCP port 80, for example, is by default associated with the HTTP protocol, indicating that the encapsulated data is most likely related to a ...
... port numbers are frequently used for drawing conclusions on the encapsulated application data. TCP port 80, for example, is by default associated with the HTTP protocol, indicating that the encapsulated data is most likely related to a ...
40. lappuse
... port 80 (i.e., a well-known HTTP port) by typing > telnet www.elsevier.com 80 [return] at the command prompt. (Do not type the '>' character, it just represents the command prompt.) Hit the [return] key as indicated and wait for the ...
... port 80 (i.e., a well-known HTTP port) by typing > telnet www.elsevier.com 80 [return] at the command prompt. (Do not type the '>' character, it just represents the command prompt.) Hit the [return] key as indicated and wait for the ...
62. lappuse
... port number (the number assigned by the network operator for proxy use), perhaps 8080 or 8000. Now, every user request will be sent to the forward proxy, rather than directly to the origin server. Referring to Figure 3.2 we can follow ...
... port number (the number assigned by the network operator for proxy use), perhaps 8080 or 8000. Now, every user request will be sent to the forward proxy, rather than directly to the origin server. Referring to Figure 3.2 we can follow ...
Saturs
1 | |
25 | |
53 | |
Chapter 4 Caching Techniques for Streaming Media | 81 |
Chapter 5 Navigating Content Networks | 109 |
Chapter 6 PeertoPeer Content Networks | 147 |
Chapter 7 Interactive Content Delivery Instant Messaging | 179 |
Chapter 8 Beyond Web Surfing Content Services | 217 |
Chapter 10 Standards Efforts | 279 |
Chapter 11 Summary and Outlook | 299 |
AppendixXML Basics | 311 |
Glossary | 313 |
RFC References | 325 |
References | 331 |
Index | 345 |
Chapter 9 Building Content Networks | 263 |
Citi izdevumi - Skatīt visu
Content Networking: Architecture, Protocols, and Practice Markus Hofmann,Leland R. Beaumont Ierobežota priekšskatīšana - 2005 |
Content Networking: Architecture, Protocols, and Practice Markus Hofmann (Computer scientist),Leland R. Beaumont Priekšskatījums nav pieejams - 2005 |
Bieži izmantoti vārdi un frāzes
allows application message architecture audio bandwidth browser cache callout protocol callout server Chapter client request communication connection content consumer content delivery content delivery network content networking content providers content services cookie defined described device distributed document Domain Name Domain Name System endpoints Ethernet example Figure format Global Gnutella header host ICAP ICAP client ICAP server identified IETF implement instant messaging interactive interception proxies Internet IP address Layer load MSRP multicast multimedia name server Napster network provider object operation OPES processor origin server packet peer-to-peer peer-to-peer networks peers port presence information Profile resource response retrieve reverse proxy Router RTSP scalability sends servent service activation point service node session specification standards streaming media switch tion traffic transaction transport protocol typically UDDI VoiceXML Web cache Web server wireless WSDL XMPP