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.

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

Use W3C API to collect data on specs #47

Open
dontcallmedom opened this issue Sep 3, 2015 · 1 comment
Open

Use W3C API to collect data on specs #47

dontcallmedom opened this issue Sep 3, 2015 · 1 comment
Milestone

Comments

@dontcallmedom
Copy link
Contributor

No description provided.

@dontcallmedom dontcallmedom added this to the November 2015 edition milestone Sep 3, 2015
dontcallmedom added a commit that referenced this issue Sep 3, 2015
Temporary until #47 gets done
@dontcallmedom
Copy link
Contributor Author

I've experimented with it in https://github.com/w3c-webmob/mobile-web-app-standards/tree/w3capi ; at the moment, this doesn't seem to be a credible alternative to the ad-hoc RDF parsing, because fetching 200 or so resources from the API server is too slow.

While I initially thought this would not be an issue (since after all it only affects the production phase, it doesn't change anything to the "published" version), it is slow enough that reloading the in-progress document becomes painful, and thus makes the overall update process too cumbersome.

Probably worth revisiting when w3c/w3c-api#60 lands, in which case one can hope that beyond the "first" load, reloads should be reasonably faster.

An alternative (or a complement) is to integrate a Service Worker layer and use a cache-first strategy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant