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

Charles Iliya Krempeaux supercanadian at gmail.com
Tue Oct 25 14:39:43 PDT 2005


On 10/22/05, James Graham <jg307 at cam.ac.uk> wrote:


> So why not enforce this case by making the client do a redirect as soon
> as it receives a response from the original URL:
> <a href="tracker.cgi" redirect="destination.html">
> On receiving a response from tracker.cgi the client would redirect to
> destination.html, irrespective of the contents of the response. It would
> allow the correct destination to be displayed in the status bar which,
> as far as I can tell, is the only merit of the original 'ping' proposal,
> but still has the disadvantage that no-one would use it (since a UA
> could easily disable contacting tracker.cgi,  making it useless for
> advertisers). It does, however,  have a reasonable backward
> compatibility story (tracker.cgi would typically take a URL parameter
> which it would redirect to). The big problem is that it seems horrible
> to implement, as one has to have special handling at the network level
> for requests initiated from a link with a redirect attribute.

One disadvantage of this is that you do not have multiple pings. 
(Which is often needed for advertising situations.)

See ya

     Charles Iliya Krempeaux, B.Sc.

     charles @ reptile.ca
     supercanadian @ gmail.com

     developer weblog: http://ChangeLog.ca/
 Never forget where you came from

More information about the whatwg mailing list