40
edits
m (3 comments) |
|||
| Line 5: | Line 5: | ||
==== RDF caching and reloading ==== | ==== RDF caching and reloading ==== | ||
I think security prevents a non-chrome page from reloading rdf datasources right now. Does the above imply that in v2 a template will support a "reload" mechanism for named datasources? There may be security issues with reloading chrome etc but perhaps you only allow reloading of remote data sources. | I think security prevents a non-chrome page from reloading rdf datasources right now. Does the above imply that in v2 a template will support a "reload" mechanism for named datasources? There may be security issues with reloading chrome etc but perhaps you only allow reloading of remote data sources. | ||
==== RDF templates and RDF loading ==== | |||
A big shortcoming of rdf templates now is that they seem to load data sources synchronously, blocking the browser. They seem to load the datasource as part of template parsing which doesn't allow a page to register as a builder listener and so catch when the first build of an element completes. As part of version 2, I think loading should be asynchronous and there should be an event like "datasourceLoaded". | |||
edits