Skip to Content.
Sympa Menu

metadata-support - [Metadata-Support] optimizing metadata refresh

Subject: InCommon metadata support

List archive

[Metadata-Support] optimizing metadata refresh

Chronological Thread 
  • From: Tom Scavo <>
  • To: "" <>
  • Subject: [Metadata-Support] optimizing metadata refresh
  • Date: Mon, 23 Mar 2015 14:21:50 -0400

On the production server (which serves aggregates), we
have the following attributes on the root element:

/md:EntitiesDescriptor/@validUntil? (currently 14d)
/md:EntitiesDescriptor/@cacheDuration? (currently NONE)

I've always thought the optimal validUntil value should be around 4
days but we're a long way from achieving that goal. On the Metadata
Consumption wiki page [1], we recommend that clients attempt a refresh
every hour (which is cacheDuration, right?). Since metadata is
typically signed once a day and the server supports HTTP Conditional
GET, I'm not sure that is optimal either (but I'm not too concerned
about it).

On the beta server (which serves per-entity
metadata), we have the following attributes on the root element:

/md:EntityDescriptor/@validUntil? (currently 14d)
/md:EntityDescriptor/@cacheDuration? (currently 6h)

I doubt these values are optimal. (This is a beta server, which is why
I haven't brought this up before now.) It's a fact that per-entity
metadata doesn't change near as often as aggregate metadata. Should
this fact be factored into the parameters somehow?

My gut tells me that validUntil should be large while cacheDuration
should be small. Does this sound right?



Archive powered by MHonArc 2.6.16.

Top of Page