Who drives (in)validation?

• Server-driven object invalidation

  • server push invalidations to clients
  • allow immediate invalidation
  • server can control “invalidation latency” & load
  • works for IP multicast, scalable

• Client-driven volume validation

  • client poll for updates to a volume of objects
  • client can react to failures
  • client can control “invalidation latency” & load

Combine server and client-driven modes

Previous slide

Next slide

Back to first slide

View graphic version