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

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

From: Charles Iliya Krempeaux <supercanadian@gmail.com>
Date: Fri, 21 Oct 2005 15:53:57 -0700
Message-ID: <84ce626f0510211553r6690147ej479e93503a8e14a1@mail.gmail.com>
Hello,

On 10/21/05, Ian Hickson <ian at hixie.ch> wrote:

[...]

> > Back to "feature detecting" though.  Maybe if we had a kind of loopback
> > "ping" that would work.  (If that makes sense.)  That way a document
> > could initiate a "ping" to somewhere it would be able to detect.
>
> You can detect whether the UA supports it or not by putting the attribute
> in uppercase:
>
>    <a href="http://example.com" PING="redirect?uri=http%3A%2F%2Fexample.com">

Is this proposal doing URI construction?  I.e., taking what's in
"href" and what's in "ping" and gluing them together?

Or is it just "hitting" -- making an hidden HTTP GET request of each
token in the "ping" attibute?

I think the later would be more better.  (At least from the point of
view of someone writing advertising software.)  So, I'd prefer
something like:

    <a href="http://advertisers-site.dom/"
ping="http://advertising-network.dom/ping-me
http://publishers-site.dom/ping-me">click me</a>

So then when the user clicks on the link, the go to what's in the
"href" -- to http://advertisers-site.dom/ .  But the user's browser
also "pings" -- makes an hidden HTTP GET -request - of the 2 URI's:
http://advertising-network.dom/ping-me and
http://publishers-site.dom/ping-me .


See ya

--
     Charles Iliya Krempeaux, B.Sc.

     charles @ reptile.ca
     supercanadian @ gmail.com

     developer weblog: http://ChangeLog.ca/
___________________________________________________________________________
 Never forget where you came from
Received on Friday, 21 October 2005 15:53:57 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:43 UTC