Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Cache-detecting bandwidth estimation #324

Closed
joeyparrish opened this issue Apr 6, 2016 · 1 comment
Closed

Cache-detecting bandwidth estimation #324

joeyparrish opened this issue Apr 6, 2016 · 1 comment
Labels
status: archived Archived and locked; will not be updated status: infeasible The requested feature is not currently feasible type: enhancement New feature or request
Milestone
v2.0.0

Comments

@joeyparrish
Copy link
Member

v2's default bandwidth estimator should be able to detect and ignore hits from the browser's cache. This will have to be a statistical heuristic, since there is no robust way of getting this information directly.
@joeyparrish joeyparrish added the type: enhancement New feature or request label Apr 6, 2016
@joeyparrish joeyparrish added this to the v2.0.0 milestone Apr 6, 2016
@TheModMaker TheModMaker self-assigned this Apr 21, 2016
@joeyparrish joeyparrish reopened this May 5, 2016
shaka-bot pushed a commit that referenced this issue May 5, 2016
@joeyparrish
Revert "Make bandwidth estimator cache friendly."
9388c1e 
This reverts commit 60d2944.

Closes #367
Reopens #324

Change-Id: I4302469a319b30f1ce502554348fd69726a50c58
@joeyparrish joeyparrish added the status: infeasible The requested feature is not currently feasible label Aug 29, 2016
@joeyparrish
Copy link
Member Author

There does not seem to be a good way to do this without introducing additional CORS requirements.

@shaka-project shaka-project locked and limited conversation to collaborators Mar 22, 2018
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Apr 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
status: archived Archived and locked; will not be updated status: infeasible The requested feature is not currently feasible type: enhancement New feature or request
Projects
None yet
Milestone
v2.0.0
Development

No branches or pull requests
3 participants
@TheModMaker @joeyparrish @shaka-bot