It definitely should be a POST, because the action performed by it is not
idempotent. See [1].
I agree is seems logical to use POST - the actual URI being visited by the
user likely would be in the content body (although a request header similar
to Referer could be used) and no state from the
On Sat, 22 Oct 2005 00:14:46 +0300, Ian Hickson [EMAIL PROTECTED] wrote:
On Fri, 21 Oct 2005, Charles Iliya Krempeaux wrote:
...
Oh, I know. My salary comes almost entirely from Web advertising. :-)
...
As currently defined the ping= attribute takes a space-separated list
of
URIs, so
J. Graham wrote:
On Sat, 22 Oct 2005, Lachlan Hunt wrote:
It could be defined in reverse, where the ping attribute (probably
given a more suitable name, but I'll use ping for now) could be
advisory information about the final destination and the href
attribute defines the ping destination,
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
