Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Metrics should show complete downloads | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Unknown <non-migrated> |
Component: | Website general issues | Assignee: | Unknown <non-migrated> |
Status: | CLOSED WONT_FIX | QA Contact: | Unknown <non-migrated> |
Severity: | Trivial | ||
Priority: | P3 | CC: | issues, zahedab2 |
Version: | current | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Unknown
2001-12-11 19:09:47 UTC
Jason's suggestion is, I believe, the method that goolie was using for a while. It works to a point it just doesn't provide us with really accurate information. Better solution is to use a method that actually sends back a "mail delivered" signal. Will look into this. -louis reassigning to support It seems to me that this is a core product enhancement request for the server to record a "completed" download somehow. I'll discuss with louis and pass this on to product management as soon as I can. looking at jason's suggestion: # of downloads * size = the full number of bytes that would be download if all downloads were full and perfect # of downloads * size / Number of bytes actually downloaded = "Perfect download bytes" / "Actual download bytes" = "Average % completion of each download" Even if we, say, find out that, on average, downloads got to be 78% complete, that does NOT mean that 78% of downloads were complete. Quite the contrary. We can't find out what percent of downloads were complete from these numbers. The only way to actually do that is to have a "download delivered" signal, as Louis mentions. This should be technically possible, but would be a significant enhancement. Does my analysis make sense to all? Zaheda, what do you think? I'm going to set this to resolved. Please reopen if you have further thoughts about this. As mentioned on the qa dev list on March 5th I will close all resolved duplicate issues. Please see this posting for details. First step in IssueZilla is unfortunately to set them to verified. As mentioned on the qa dev list on March 5th I will close all resolved <wontfix/duplicate/worksforme/invalid> issues. Please see this posting for details. moving to another subcomponent to allow removal of the current subcomponent. |