Opened 8 years ago

Closed 8 years ago

#3 closed defect (fixed)

Section 4.1.3: Scalability

Reported by: mglt.ietf@… Owned by: cyrus@…
Priority: major Milestone:
Component: caldav-timezone-ref Version:
Severity: Candidate WG Document Keywords:

Description (last modified by mglt.ietf@…)

Draft: draft-douglass-timezone-service-11

"Clients SHOULD poll for such changes at least once a day. A server acting as a local provider, caching timezone data from another server, SHOULD poll for changes once per hour. See Section 9 on expected client and server behavior regarding high request rates."

In future version I would like to elaborate a bit more how this system is scalable. Maybe that is already in the document and I missed it. I can provide text too.

Change History (2)

comment:1 Changed 8 years ago by lear@…

  • Severity changed from - to Candidate WG Document

comment:2 Changed 8 years ago by mglt.ietf@…

  • Component set to caldav-timezone-ref
  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from new to closed

the scalability issue raised by this thread concerns data truncation which remains an open thread in issue #15.

Note: See TracTickets for help on using tickets.