Serve static version of the main WADL file
Bug #245368 reported by
Leonard Richardson
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Gary Poster |
Bug Description
Currently every client is going to fetch our main WADL file every time it starts up. This is ridiculously expensive, given that the WADL file will never change over the course of a release and that it's very expensive to generate. We should export it to a static file and serve it through Apache with a long-term caching directive.
Changed in launchpad: | |
assignee: | nobody → flacoste |
importance: | Undecided → High |
milestone: | none → 1.99 |
status: | New → Triaged |
Changed in launchpad: | |
milestone: | 1.99 → none |
Changed in launchpad-foundations: | |
assignee: | flacoste → nobody |
Changed in launchpad-foundations: | |
assignee: | nobody → garyposter |
milestone: | none → 2.1.11 |
Changed in launchpad-foundations: | |
status: | Triaged → In Progress |
Changed in launchpad-foundations: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Since the WADL file is retrieved via content- negotiation, I don't think we could make it served by apache. Serving a static file in the app server would still be a good idea.