Hello Greg,<br><br><div><span class="gmail_quote">On 2/16/06, <b class="gmail_sendername">Greg Bildson</b> <<a href="mailto:gbildson@limepeer.com">gbildson@limepeer.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br>> -----Original Message-----<br>> From: <a href="mailto:p2p-hackers-bounces@zgp.org">p2p-hackers-bounces@zgp.org</a> [mailto:<a href="mailto:p2p-hackers-bounces@zgp.org">p2p-hackers-bounces@zgp.org</a>]On<br>
> Behalf Of Charles Iliya Krempeaux<br>><br>> A "P2P conditional get" (sent by the client) would tell the server NOT<br>> to send the requested document if there is an alternative way of<br>> getting the document via a P2P technology supported by the client.
<br>> (The client would tell the server which P2P technologies it supports.)<br>> (This "P2P conditional get" would work similar to the "If-None-Match"<br>> and "If-Modified-Since" "conditional get" headers.).
<br>><br>> For example, it might be something like:<br>><br>> X-If-No-Alternate: bittorrent, something-else, magnet<br>><br>> First, this says that the client supports the protocols: "bittorrent",
<br>> "something-else", and "magnet". It also says it prefers "bittorrent"<br>> first, then "something-else", and then "magnet".<br><br><br>Are these hypothetical options for future web browsers? I take it that
<br>there would be no way to make a current browser actually communicate what<br>the computer it's running on supports in this way right now?</blockquote><div><br>First let me say that my proposal actually changed a bit. As I discussed things with others on this mailing list (in other messages in this thread/tree of e-mails) I modified my proposal. Right now (in my proposal) the information that I previously had being returned with the "Location" header is now being returned with the "Link" header. (See section
<a href="http://19.6.2.4">19.6.2.4</a> of RFC 2068 for more information on the "Link" header.) Basically though the "Link" header basically has the same semantics as the HTML <link> element.<br>
<br>Given that,... the header I was proposing is now called "X-If-No-Link".<br><br>So, getting back to you question... Yes, these are ideas for future browsers. My project (that is motivating this work) is being built on the Mozilla application framework (using
<a href="http://developer.mozilla.org/en/docs/XULRunner">XULRunner</a>). So I could imagine it very easily getting into Firefox via an extention. (And if people find it useful and it becomes popular I could see it getting into the mainstream web browsers. But as far as my work is concerned it doesn't have to.)
<br><br>Now, as far as current browsers are concerned, if you mandate that you don't want to install anything, then you could do some of this via an XmlHttpRequest (or a GM_xmlHttpRequest is you are using Greasemonkey). You could make a request and set all the "X-If-No-Link" headers that you want. And then when you get the response, you could check for the "Link" headers.
<br><br><br> </div></div>See ya<br clear="all"><br>-- <br> Charles Iliya Krempeaux, B.Sc.<br><br> charles @ <a href="http://reptile.ca">reptile.ca</a><br> supercanadian @ <a href="http://gmail.com">gmail.com</a><br>
<br> developer weblog: <a href="http://ChangeLog.ca/">http://ChangeLog.ca/</a><br>___________________________________________________________________________<br> Make Television <a href="http://maketelevision.com/">
http://maketelevision.com/</a>