Univention Bugzilla – Full Text Bug Listing |
Summary: | AppCenter starts N threads | ||
---|---|---|---|
Product: | UCS | Reporter: | Dirk Wiesenthal <wiesenthal> |
Component: | App Center | Assignee: | App Center maintainers <appcenter-maintainers> |
Status: | RESOLVED WORKSFORME | QA Contact: | |
Severity: | normal | ||
Priority: | P5 | CC: | best, gohmann, hahn, klaeser, walkenhorst |
Version: | UCS 3.2 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | Linux | ||
URL: | http://tools.ietf.org/html/rfc2616#section-8.1 | ||
What kind of report is it?: | Bug Report | What type of bug is this?: | 2: Improvement: Would be a product improvement |
Who will be affected by this bug?: | 4: Will affect most installed domains | How will those affected feel about the bug?: | 1: Nuisance – not a big deal but noticeable |
User Pain: | 0.046 | Enterprise Customer affected?: | |
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | ||
Max CVSS v3 score: | |||
Bug Depends on: | 32935, 34834 | ||
Bug Blocks: |
Description
Dirk Wiesenthal
2014-05-12 01:31:29 CEST
We could also employ HEAD requests (=GET requests without the body) in order to determine whether the file has changed or not. Also see Bug 32935, comment 4 in order to speed up processing multiple requests. (In reply to Alexander Kläser from comment #1) > We could also employ HEAD requests (=GET requests without the body) in order > to determine whether the file has changed or not. Look at the code on why this wouldn't help: The app center already caches all files locally and skips those already present: file dates are NOT compared, so the app-center never fetches a file twice and never updates a file already downloaded (expect index.json.gz). Even better would be "If-Modified-Since", as this combines the benefit of HEAD with GET: If the file is not modified, a simple "304 NOT MODIFIED" is returned. Otherwise a normal "200 OK" is performed, which saves one round-trip which would be needed in your modified case. Other options: 1. Embed all images base64 encoded in the index.json.gz? 2. Use a version control system like SVN: then you can ask for updates since revision-last-time. 3. Fetch images only on demand and only then cache them locally. Different approach: storing App Center meta data in a separate package at release time, then only a few file updates/new files will be downloaded. Was implemented at some point. |