Caching of discovered Yadis service definitions / best practices?

[Drummond Reed]

Ah, I understand. XRI resolution infrastructure is young so practices are
just coming into play. Furthermore XRIs may have different time-to-live
chacteristics.

FWIW, XDI.org is presently planning to establish the initial TTL for global
XRIs at between 24 and 48 hours, and strongly encourages caching by both
proxy and local resolvers for this period as this helps with both load and
performance.

=Drummond 

-----Original Message-----
From: Johannes Ernst [mailto:jernst+lists.danga.com at netmesh.us] 
Sent: Friday, March 03, 2006 7:02 PM
To: Drummond Reed
Cc: 'YADIS List'
Subject: Re: Caching of discovered Yadis service definitions / best
practices?

Drummond,

I know there's all the machinery you guys have defined that we can  
essentially get for free in Yadis ...

What I meant to ask was about implementation practices.

Thanks,


Johannes.


On Mar 3, 2006, at 16:45, Drummond Reed wrote:

> Johannes,
>
> What's nice is that all the cache support is built into the XRD  
> vocabulary
> (the Expires element) plus all the normative rules in the XRI  
> Resolution
> spec (the famous final Working Draft 10 of which should finally be  
> out next
> week).
>
> So the Yadis spec could just reference or add its own policies  
> around that.
>
> =Drummond
>
> -----Original Message-----
> From: yadis-bounces at lists.danga.com [mailto:yadis- 
> bounces at lists.danga.com]
> On Behalf Of Johannes Ernst
> Sent: Friday, March 03, 2006 3:44 PM
> To: YADIS List
> Subject: Caching of discovered Yadis service definitions / best  
> practices?
>
> The first time a Relying Party (RP) encounters a Yadis-enabled URL,
> the RP will likely want to obtain the Yadis document associated  
> with it.
>
> The second time the RP encounters the same URL, it may or may not
> want to re-resolve. If a year has passed, it probably should re-
> resolve. If a second has passed, re-resolving is almost certainly
> going to produce the same information.
>
> Of course, we agreed that the Yadis 1.0 spec will be silent on this
> issue, and that decision was the right one.
>
> I have a question for implementors: Do you cache? Or not? Or in the
> next version? ;-)
>
> If you cache, for how long do you cache? Or what is your policy? I
> suspect that most people won't cache at this point in time, in
> particular as resolution loads are still low. But if you did, what
> would your policy be and why?
>
>
>
>
> Johannes Ernst
> NetMesh Inc.
>
>

Johannes Ernst
NetMesh Inc.