<< 1 >>
Rating: 
Summary: It's not an exciting read...
Review: ...but it is very thorough.
Rating:
Summary: Web Protocols and Practice
Review: I give it the best rating for being instantly useful. It is comprehensive; buy this one first and use it for basic and advanced topics. HTTP section is especially useful. The book is timely: Multimedia and web caching are hot topics and well covered. It also forward thinking, touching on research topics for the web.
Rating:
Summary: "The" book of the web
Review: Protocol and practice.... unlike 21 days in HTML, the authors teach me something big...
Rating:
Summary: If you read only one book on HTTP, READ THIS!!!
Review: This is a fabulous book, technically competent, well-written, easy to read and well-organized. It comprehensively covers all the tech-weenie needs to know about clients, proxies, servers, HTTP, and a bunch more without drowning you in math or killing you softly with a gazillion irrelevant details. I found the last chapter, the "Research Perspectives," to be particularly up-to-date and useful. There is a ton of information about HTTP floating around out there. Figuratively speaking, Rexford and Krishnamurthy have taken as their input the coal and produced as their output this diamond.
Rating:
Summary: great book for researchers on web
Review: This is the most comprehensive book on HTTP protocols that I have seen. It covers all related areas, such as web caching, web workloads, and most importantly, possible research directions. (though it has the bias of the authors ;-)) from the prespective of research. Moreover, it is a very timely book, you will find the bibliography of this book is very useful.
Rating:
Summary: It's not an exciting read...
Review: You've built a B2C or B2B web service. You get great response time from your office, but there are times when your customers across the country report poor performance. This book with help you understand the entire path between browser and web server and how Internet latency and intermediaries like Proxy servers add to transaction delay. This is the only source that I've seen that a) Defines HTTP 1.1 and b) describes the relationship between HTTP and the TCP/IP protocol stack, making recommendations on how to tune the stack to reduce the effect of latency. You'll learn that many of TCP's flow control mechanisms were designed for FTP, Telnet and Rlogin and some default settings are not optimized, or even appropriate for HTTP.
Rating:
Summary: Understand Web Performance
Review: You've built a B2C or B2B web service. You get great response time from your office, but there are times when your customers across the country report poor performance. This book with help you understand the entire path between browser and web server and how Internet latency and intermediaries like Proxy servers add to transaction delay. This is the only source that I've seen that a) Defines HTTP 1.1 and b) describes the relationship between HTTP and the TCP/IP protocol stack, making recommendations on how to tune the stack to reduce the effect of latency. You'll learn that many of TCP's flow control mechanisms were designed for FTP, Telnet and Rlogin and some default settings are not optimized, or even appropriate for HTTP.
<< 1 >>
| 
