Amazon Web Services Error
Unfortunately we were unable to retrieve details of the product code you requested from Amazon.com or our local cached copy of previous responses. There may be several reasons for this, some of which include, but are not limited to:-
- Incorrect product code (156592536X)
- Problems with the Amazon XML returned from the server
- An empty XML document may have been returned
- The XML data may have been corrupt or unusable
- An unexpected character may have prevented XML processing
- There were no cached details available to display when details could not be retrieved
This error may be temporary or permanent. Please feel free to try again or follow the link to Amazon.com to check out the specific product details. In the meantime, the site owner has been sent a mail containing enough information to be able to reproduce the error. We hope to be able to resolve this error in the future.
See XML Document RequestedRosie says...
I bought this one because I knew I was using more server resources than I needed and I wanted to know what sort of things I could do to reduce unnecessary strain on the server.
After reading Web Caching, I soon learned that there was more to the topic than meets the eye. The chapter on politics of caching makes for interesting reading no matter who you are on the web; covering topics such as copyright, privacy and trust, offensive content and maintaining content integrity.
I also learned more about just how important caching is to the web, which convinced me that I really should make my web pages as cache friendly as possible. Not only does the creation of cache friendly pages speed up the delivery of content, but it can also reduce the cost of hosting individual web sites!
As you can imagine, there is a lot of discussion in the book about the communications between server and browser that many of us do not see. Most of this discussion focuses on the use of HTTP headers, but there is little discussion about using various scripting technologies to over-ride the default headers that are used by the server. Even an Appendix chapter to compliment the Perl example given would have been nice, as not everyone has access to their server's settings or knows how to use their language of choice to generate server headers.
All in all Web Caching is an interesting book to read as it certainly makes you think about the issues surrounding the subject. I can't help feeling however that this book was written mainly for the server administrators, as practical examples for those that have no direct control of the server are somewhat lacking...
- Readability: 5
- Reference: 4
- Reusability: 3
- Examples: 3
- User Level: All
- Score: 15/20
Chapter List
- Introduction
- How Web Caching Works
- Politics of Web Caching
- Configuring Cache Clients
- Interception Proxying and Caching
- Configuring Servers to Work with Caches
- Cache Hierarchies
- Intercache Protocols
- Cache Clusters
- Design Considerations for Caching Services
- Monitoring the Health of Your Caches
- Penchmarking Proxy Caches
- Analysis of Production Cache Trace Data
- Internet Cache Protocol
- Cache Array Routing Protocol
- Hypertext Caching Protocol
- Cache Digests
- HTTP Status Codes
- U.S.C. 17 Sec. 512. Limitations on Liability Relating to Material Online
- List of Acronyms
Other Information
A sample chapter, Interception Proxying and Caching, is available from the O'Reilly Web Site. The contents list, book cover image and sample chapter are used with kind permission from O'Reilly.