Comments on: Parameterizing SVG and HTML

By: Jeff Schiller

Jeff Schiller — Wed, 26 Nov 2008 22:45:57 +0000

Update: Apparently browsers send in the attributes of the element to the plugin as well the elements. HTML 5 favors the plugin over the native content handler even more than I thought it did before.

By: Jeff Schiller

Jeff Schiller — Fri, 25 Jul 2008 19:19:16 +0000

@Kevin: You got it on the second try, but instead of PHP, you can do the same thing with HTML files (url.html?caption=A) meaning parameters can be processed by JS in the browser.

By: Kevin H

Kevin H — Fri, 25 Jul 2008 18:16:18 +0000

Oh, Wait!

I think I get it now. I suspect that what you want to be able to do is the equivalent of calling url.php?caption=A and then url.php?caption=B without making 2 separate calls to the server (loading url.php out of the cache on the second fetch, and letting it process the caption=B parameter client-side). For this example usage, you are right, query strings are completely inappropriate.

While I’m too unfamiliar with SVG to say if there is an alternate way of doing what you want, I think typically this sort of behavior is limited to <SCRIPT>

By: Kevin H

Kevin H — Fri, 25 Jul 2008 18:04:58 +0000

> In my experiments with PHP, I found that query parameters are a good way to ensure the browser actually re-fetches a document and doesn’t rely on the document in the cache.

I think you need to re-run your experiment, or publish your methodology and findings so they can be scrutinized. Because the presence of a query string in a GET should not, in practice, adversely affect the cacheability of that request.

By: Erik Dahlström

Erik Dahlström — Fri, 25 Jul 2008 17:58:54 +0000

I agree that this is a feature that the HTML WG shouldn’t dismiss so quickly.