Skip to content
This repository has been archived by the owner on Jul 22, 2024. It is now read-only.

Reduce number of duplicated XHR requests (w/ THREE.js', albeit limited, caching mechanisms) #91

Closed
cvan opened this issue Oct 5, 2016 · 1 comment
Labels
ARCHIVED CLOSED at time of archiving

Comments

@cvan
Copy link
Contributor

cvan commented Oct 5, 2016

Some are loaded only 2 times, and others are loaded 12+ times. Here are a few examples of the 191 requests:

screen shot 2016-10-05 at 8 14 55 am
screen shot 2016-10-05 at 8 14 47 am
screen shot 2016-10-05 at 8 13 11 am
screen shot 2016-10-05 at 8 14 36 am
screen shot 2016-10-05 at 8 14 24 am
screen shot 2016-10-05 at 8 14 11 am
screen shot 2016-10-05 at 8 14 01 am
screen shot 2016-10-05 at 8 13 11 am

@cvan cvan changed the title Use THREE.js' asset caching to avoid unnecessary XHR calls Reduce number of duplicated XHR requests (w/ THREE.js', albeit limited, caching mechanisms) Oct 5, 2016
@cvan
Copy link
Contributor Author

cvan commented Oct 5, 2016

We had and have several issues on file for A-Frame. @ngokevin and @dmarcos closed a ton of them by doing a lot of smart stuff to make asset management work well. There are still a ton of open issues in three.js, though there are ways to work around it (by not directly using the loaders, using in-memory objects to cache, using the Cache API [introduced by the Service Worker API], or as a last resort IndexedDB could be used).

Relevant three.js issues:

@cknowles-admin cknowles-admin added the ARCHIVED CLOSED at time of archiving label Jul 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ARCHIVED CLOSED at time of archiving
Projects
None yet
Development

No branches or pull requests

2 participants