You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Eric suggested pulling the data found on the activity page. That data is available at /wp-json/buddypress/v1/activity. (OLC)
Traffic for OLC is rather low. Using the raw activity feed would be sufficient for a while. Later, the need could arise for fetching only "hot" or popular threads.
The text was updated successfully, but these errors were encountered:
@Ebcosio , I think the OLC activity data feed lends itself to caching better than the events data, which needed to be kept up-to-date (or at least kept only in page cache).
As such, I think we could cache the activity feed in a transient. That could be very fast if CLT decided to use in-memory caches for their WP sites. Even if they don't, it would still be faster than calling OLC every time.
I think we could make the cached OLC data expire every 6 hours or so. Overall, what do you think about caching the OLC data?
Eric suggested pulling the data found on the activity page. That data is available at
/wp-json/buddypress/v1/activity
. (OLC)Traffic for OLC is rather low. Using the raw activity feed would be sufficient for a while. Later, the need could arise for fetching only "hot" or popular threads.
The text was updated successfully, but these errors were encountered: