Cache
The basic information from these clients can be used on any page. To prevent frequent API requests from slowing down the load speed, we recommend implementing caching on the client side.
We also recommend caching the currently logged in account and user profile for, say, 1 minute to avoid frequent requests to the UI. When the user performs an interactive function, such as liking, posting, changing the profile, etc., it can be cached again.
Cache Time
/api/fresns/v1/global/configs?keys=cache_datetime,cache_minutes
cache_datetimeDatetime of last server-side configuration.cache_minutesRecommend that the client caches be saved for a maximum number of minutes, with a value ofnullindicating no limit. If there is no limit, it is suggested to periodically request the interface and only obtain thecache_datetime,cache_minutesconfiguration, compare the validity period with that of the local one. If they are inconsistent, it means that the server has updated the configuration, so please re-cache it.