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

Unclear management of the resource #10

Open
AndySky21 opened this issue Apr 3, 2015 · 1 comment
Open

Unclear management of the resource #10

AndySky21 opened this issue Apr 3, 2015 · 1 comment

Comments

@AndySky21
Copy link
Contributor

This internal data can be modified by Javascript if needed, separate from modifying the DOM

There could be an entire subset of stuff inside <head> element to be changed: namely, <title> element for the page (it is important for bookmarking and interface), metadata (e.g. related resources, tags, description, and all that meta information used by native applications - see wiki.whatwg.org/wiki/MetaExtensions and microformats.org/wiki/existing-rel-values). Your model requires all these aspects to be updated by Javascript. I agree that current JS framework don't do that, but as a matter of fact a native application should be able to do it. It shouldn't be that difficult using model attributes - but you have to suggest it.

you could export this data for form processing if you wish.

Please make this clearer.

This internal data can also be push updated by a server or connected directly to a local database for caching or persistence - the browser manages this now, instead of the web developer/Javascript.

These are two very different cases that should be taken into account separately.

  • push update relies upon server/client data exchange. Consider elaborating a user interface to delay/pause push updates, or you'll end up with the same criticism moved against <meta refresh>
  • data cache could be somehow useful. As a matter of fact you are suggesting that only data, and not the whole "resource"* should be cached. It represents economy in terms of used memory, but it requires page reparsing every time a resource URI is invoked by the user agent.

*let's call "resource" a template structure filled in with non-initial fetched data. This will allow us to distinguish it from "page", which is the object initially sent to the client.
@mozumder
Copy link
Owner

mozumder commented Apr 5, 2015

Yes the the push updates and data cache use cases will be expanded upon later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mozumder @AndySky21