Reliable ETag for GET on rolled-up calendar data

[macosforgebot]

apm@… originally submitted this as ticket:466

---

[macosforgebot]

@wsanchez originally submitted this as comment:1:⁠ticket:466

• Type changed from Feature to Defect
• Owner changed from @wsanchez to @cyrusdaboo
• Priority changed from 5: Not set to 3: Important

---

Fair enough

[macosforgebot]

apm@… originally submitted this as comment:2:⁠ticket:466

---

Oh ... and one note:

The 2.4 implementation of the ETag doesn't really save you any time, since it goes through the entire rolling up of events and only considers the ETag afterwards. It seems to rely on a Twisted asumption that GET and HEAD are always so fast, that it doesn't matter. However, generating rolled up calendar data is not that fast.

[macosforgebot]

@wsanchez originally submitted this as comment:9:⁠ticket:466

• Milestone set to Later

---

Later; post dumping web2

[macosforgebot]

@wsanchez originally submitted this as comment:10:⁠ticket:466

---

Expiring old bugs with unknown impact