Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] distribution of aggregate metadata

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] distribution of aggregate metadata


Chronological Thread 
  • From: Jorj Bauer <>
  • To: "Cantor, Scott" <>
  • Cc: "Walter Forbes Hoehn (wassa)" <>, Scott Koranda <>, Tom Scavo <>, Nick Roy <>, Chris Phillips <>, Per-Entity Metadata Working Group <>
  • Subject: Re: [Per-Entity] distribution of aggregate metadata
  • Date: Thu, 11 Aug 2016 16:04:59 -0400
  • Ironport-phdr: 9a23:cTloSxJk6P0omFs9e9mcpTZWNBhigK39O0sv0rFitYgXI/3xwZ3uMQTl6Ol3ixeRBMOAtKIC1rGd6v2ocFdDyKjCmUhKSIZLWR4BhJdetC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TWapAQfERTnNAdzOv+9WsuL15z2hKiO/MiZSAxOmD2nJftJJxKqsU+Z4sIfh5dlMOBr4hzSvz1Fd/kAlk1yIlfGvRHm5I+a9YNu6WwEufU79eZcXKDie6l+QLBFWmd1e1sp7dHm4EGQBTCE4WERByBPykJF

This all sounds a whole lot like reinventing DNS.

Sent from my iPhone

On Aug 11, 2016, at 15:57, Cantor, Scott
<>
wrote:

>> So far, I’ve only heard option “a” discussed. What this buys you is simply
>> a
>> cache that spans restarts for the entities already “seen” by the node.
>
> Right, and our expectation is that entities may still carry multi-day
> validity windows if they need to, particularly in the early going.
>
> We would resolve a cached instance to memory and only then be within the
> cacheDuration the document itself is advising us to use. On disk is
> basically a backstop to transparently fall into as though it came from the
> real server.
>
> -- Scott
>



Archive powered by MHonArc 2.6.19.

Top of Page