WDS.fm managed assets (templates, user objects, interest objects, etc) in local storage on the client. Each item has an expiration set in /app/routes/api/assets.coffee so GET /api/assets/ pulls and updates only what's necessary.
The new WDS.com has the foundations of this built but isn't currently caching locally.
This is needed particularly for templates, which are currently a negligible DL happening on every initial page-load.
WDS.fm managed assets (templates, user objects, interest objects, etc) in local storage on the client. Each item has an expiration set in /app/routes/api/assets.coffee so GET /api/assets/ pulls and updates only what's necessary.
The new WDS.com has the foundations of this built but isn't currently caching locally.
This is needed particularly for templates, which are currently a negligible DL happening on every initial page-load.