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 39.
2. lappuse
... server to contact and the name of the file to download. Knowing just the title and the authors of a research paper, for example, was not sufficient for retrieving an electronic copy of the paper. Moreover, the user was required to ...
... server to contact and the name of the file to download. Knowing just the title and the authors of a research paper, for example, was not sufficient for retrieving an electronic copy of the paper. Moreover, the user was required to ...
8. lappuse
... server anywhere in the world. To find and access a specific Web object, the user needs some kind of handle that identifies the object in a unique way. There are two fundamental ways for identifying objects in the Web space: a name ...
... server anywhere in the world. To find and access a specific Web object, the user needs some kind of handle that identifies the object in a unique way. There are two fundamental ways for identifying objects in the Web space: a name ...
9. lappuse
... server name, and a path. These parts are represented according to the following syntax: <protocol>://<server>/<path> The protocol part indicates the communication protocol to be used for requesting and retrieving the Web object from the ...
... server name, and a path. These parts are represented according to the following syntax: <protocol>://<server>/<path> The protocol part indicates the communication protocol to be used for requesting and retrieving the Web object from the ...
34. lappuse
Architecture, Protocols, and Practice Markus Hofmann, Leland R. Beaumont. server ... named /index.html via HTTP version 1.0. The request line is terminated by a carriage return/line feed and ... name, which is. 34 CHAPTER 2 Content Transport.
Architecture, Protocols, and Practice Markus Hofmann, Leland R. Beaumont. server ... named /index.html via HTTP version 1.0. The request line is terminated by a carriage return/line feed and ... name, which is. 34 CHAPTER 2 Content Transport.
35. lappuse
... name, which is separated by a colon from one or more attributes. The example above shows four separate header lines indicating the hostname of the addressed Web server, the date and time the request was issued, the user agent of the ...
... name, which is separated by a colon from one or more attributes. The example above shows four separate header lines indicating the hostname of the addressed Web server, the date and time the request was issued, the user agent of the ...
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