Skip to content
Discussion options

You must be logged in to vote

Plan uses the json cache to not lock the webserver.

The mechanism for this is same for older version, but what is returned by webserver is a bit different in newer version.

The update mechanism

  1. Request arrives
  2. A new task to update the data in the background is started
  3. Data is read from the cache
  4. Cached data is returned in Response (200 OK or 304 Not Changed) (Blue line in the image)
  5. Task finishes in the background
  6. Data is written to the cache (Orange line in image)

In 5.5 build 2195 or higher

Timestamp Where? What? Description
Cached JSON timestamp JSON timestamp {"timestamp": 1677912750123, "timestamp_f": "Today, 06:52", ...} Time when Plan updated the data
HTTP Cache timestamp

Replies: 3 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by xiaoyv404
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants