Advertisement
Advanced thin client solution for Linux, based on Open Source. Mix Windows and Linux applications on the same desktop.
| |||||||||||
Link FingerprintsLink FingerprintsPosted Aug 24, 2007 16:33 UTC (Fri) by bronson (subscriber, #4806)In reply to: Link Fingerprints by rfunk Parent article: Google Summer of Code: Mozilla Projects I agree 100%. IMO, best would be, as you say, to pass the hash in a separate attribute. Second best would be to put it in the query (http://mirror.com/file?sha256=abc123). But, changing the meaning of the fragment? That's just silly! Let's say I want to send someone to a specific section, sec2, in a page on a remote site. Let's say further that I need to verify that the page is *exactly* what I was expecting.
<a href="http://mirror.com/a.html#sec2" hash="sha256:abc123"> -- attribute works Let's hope they give this some more thought...
(Log in to post comments)
Link Fingerprints Posted Aug 24, 2007 16:47 UTC (Fri) by rfunk (subscriber, #4054) [Link] Hmm, I don't like putting it in the query string, since that's considered reservedfor processing by the server. The other two are explicitly for client-side processing.
|
|||||||||||