[OpenID] Summarizing my grouse with XRD

[Santosh Rajan]

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>.

On Wed, Oct 21, 2009 at 9:54 PM, Breno de Medeiros <breno at google.com> wrote:

> That requires you to build your own caching approach, which is fine,
> but actually gives you few benefits. If you use HTTP for caching, it
> will be cached in every proxy in the internet in additional to the
> client, so the benefits are exponentially higher.
>
> On the other hand, there is nothing preventing you from creating your
> own cache. If a Subject is missing you cache with a virtual Subject
> based on where you started the discovery process at.
>
> On Wed, Oct 21, 2009 at 9:22 AM, Santosh Rajan <santrajan at gmail.com>
> wrote:
> > When I spoke about cacheing in point no (2) I clearly mentioned
> > 'Applications "IN THE KNOW OF XRD's"'. So I am talking cacheing about of
> > XRD's by applications who are aware of XRD's, which is more than the
> general
> > cacheing of XRD's, like any other file you are talking about. And if i am
> > still not clear to you, what I am suggesting is that XRD's will be used
> as
> > something like hcard's, and they will cache'd in that context.
> >
> >
>
>
>
> --
> --Breno
>
> +1 (650) 214-1007 desk
> +1 (408) 212-0135 (Grand Central)
> MTV-41-3 : 383-A
> PST (GMT-8) / PDT(GMT-7)
>



-- 
http://hi.im/santosh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20091021/4d4e7c33/attachment.htm>