...
Time | Item | Who | Notes | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
5m | OpenLMIS Ref Distro 3.2 release | Josh |
| ||||||||||||||||
25m | Q&A Session on Performance Tips document | Josh | Please read and come prepared to ask questions and have a discussion on the recent Performance documents, especially the Performance Tips document. | ||||||||||||||||
25m | UI Extension Patterns followup | Nick Reid (Deactivated) |
|
Notes
HTTP Caching
A question was raised on how to support etags on the frontend. At a high level this support is:
- Store a returned etag with the resource that's returned
- Forward that etag in an if-none-match request header
- Be cognizant of the cache-control response headers - though this support is still in progress.
How that's enabled in our UI framework needs guidance.
As of this writing, there are 3 resources that support etags:
Action items
- Josh Zamor to followup on admin user
- Nick Reid (Deactivated) to followup on guidance for UI support of HTTP caching