You said that you will have to cache with a virtual subject. And that is my concern. So the onus is on a second or third party to provide a <Subject> for the XRD. You will agree with me that it doesn't beat the first party providing the <Subject>.<br>
<br><div class="gmail_quote">On Wed, Oct 21, 2009 at 9:54 PM, Breno de Medeiros <span dir="ltr"><<a href="mailto:breno@google.com">breno@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
That requires you to build your own caching approach, which is fine,<br>
but actually gives you few benefits. If you use HTTP for caching, it<br>
will be cached in every proxy in the internet in additional to the<br>
client, so the benefits are exponentially higher.<br>
<br>
On the other hand, there is nothing preventing you from creating your<br>
own cache. If a Subject is missing you cache with a virtual Subject<br>
based on where you started the discovery process at.<br>
<div class="im"><br>
On Wed, Oct 21, 2009 at 9:22 AM, Santosh Rajan <<a href="mailto:santrajan@gmail.com">santrajan@gmail.com</a>> wrote:<br>
> When I spoke about cacheing in point no (2) I clearly mentioned<br>
> 'Applications "IN THE KNOW OF XRD's"'. So I am talking cacheing about of<br>
> XRD's by applications who are aware of XRD's, which is more than the general<br>
> cacheing of XRD's, like any other file you are talking about. And if i am<br>
> still not clear to you, what I am suggesting is that XRD's will be used as<br>
> something like hcard's, and they will cache'd in that context.<br>
><br>
><br>
<br>
<br>
<br>
</div>--<br>
<div><div></div><div class="h5">--Breno<br>
<br>
+1 (650) 214-1007 desk<br>
+1 (408) 212-0135 (Grand Central)<br>
MTV-41-3 : 383-A<br>
PST (GMT-8) / PDT(GMT-7)<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><a href="http://hi.im/santosh">http://hi.im/santosh</a><br><br><br>