W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2005

[whatwg] <a href="" ping="">

From: S. Mike Dierken <mike@dierken.com>
Date: Fri, 21 Oct 2005 23:50:44 -0700
Message-ID: <20051022065041.C5FAE107AC1@legolas.dreamhost.com>

> Bearing the above in mind, I've added a section to the <a> 
> element that describes a ping="" attribute. The URIs given in 
> this attribute would be followed when the user clicks the 
> link, thus getting around the problems listed above.

Since this is effectively capturing where the user's attention is being
spent (the click event I mean), should you also define the other set of
events of interest as well?
 <a href="..." on-click-notify="myattention.org/dierken"
on-hover-notify="myattention.org/dierken"
on-copy-notify="myattention.org/dierken">Wicked Cool Stuff Here</a>

What is the request method for these notifications (the wording "the URIs
would be followed" imply retrieval)?
If POST, what is the content body?
If GET, what is the URI (generated from the href via a pattern, or static
from the downloaded html)?
Should the Referer request header also be sent (except for documents
retrieved via secure protocols)?
Should the notification event occur before, during or after the retrieval of
the href="..." resource?
Should the notification event occur for only succesful retrievals? Or should
the notification contain the response status of incomplete retrievals of the
href="..." resource?
Should the notification URIs be restricted to the same host/domain as a) the
source document b) the href="..." resource or c) unlimited?
Received on Friday, 21 October 2005 23:50:44 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:24 UTC