Comment 2 for bug 459418
Revision history for this message
| Leonard Richardson (leonardr) wrote Re: Cache is broken with multiple processes | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
We only serve the Cache-Control header for the service root (WADL and JSON), so those are the only resources for which we currently avoid round trips. But here are three reasons to like the cache anyway:
1. Those service root representations are pretty big fish to have caught. They're requested every time a Launchpad instance is created, and the WADL representation in particular is rather large. Taking launchpadlib down to one request per week for these resources was a big performance win.
2. The cache is where we store the ETags that let us make conditional GET and PATCH requests, even for resources who don't have Cache-Control headers.
3. At any time we can decide to be less conservative, and start sending Cache-Control for other documents. Then the client-side cache will be more useful. We just haven't made that decision yet.