Skip to content
distobj edited this page Oct 3, 2011 · 1 revision

DOMify currently tries to provide the document abstraction in such a way that the document's state always reflects the actual state of the information on the device. In other words, it avoids the need for an explicit "retrieval" action, such as with XMLHttpRequest. This step is avoided primarily because of the verbose nature of using XHR, but it's also of import

As an example of this shortcoming, the Geo document doesn't support the "maximumAge" fetaure because that information would ideally be expressed as message metadata used while requesting, e.g. using;

"Cache-Control: max-age=NNN"

My current thinking - ironically - is that the geolocation API is a good example of an interface that would benefit from an explicit refresh due to the high cost (read; battery) of data acquisition. It's obviously possible that other APIs might have similar needs, but I doubt it will be common. So, to avoid the XHR verboseness problem (and then the issue of defining a URI for the Geo document), this suggests a simple framework-level "refresh" mechanism (which would accept the max-age parameter). TODO.

Clone this wiki locally