Comment 2 for bug 714621
Revision history for this message
| Martin Pool (mbp) wrote Re: [Bug 714621] [NEW] Reevaluate our WADL caching strategy under continuous deployment | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
On 8 February 2011 07:40, Robert Collins <email address hidden> wrote:
> On ETAG, can we not just drop the revno and use the resulting content
> hash?
>
> As for duration, I suggest upping the cache time to one year and
> adding must-revalidate.
+1
> If we also move wadl out of the appserver
> (which we should, its static), then these things all combined will
> result in:
> - immediate detection of new WADL
> - 1 conditional request on every launchpadlib new session - but that
> will be approximately free
> - up to a years freshness when we are not changing the WADL.
Also, moving it out of the app server would let us more easy set a
last-modified date and not worry about the etag.
Doing this would probably also fix bug 607961, which is that wadl
generation is very slow/expensive. Conversely, if clients fetch the
wadl every time without that bug being fixed, it will slow them down
(30s startup delay) and perhaps load the server.