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
The RequestCache should be cleared between processing of each message to treat message processing like a request. In case any code is shared between message processing and the service itself, the RequestCache should have a common interpretation. Basically, we will be replacing this call that is currently in the RequestCacheMiddleware.
Note that for now the only cache between messages would be the shared Django cache (e.g. Memcached). We do not support a consumer level cache, and will leave that for when and if it becomes a priority.
The text was updated successfully, but these errors were encountered:
This is a just-in-case measure -- we don't know of any specific code that
handles events and relies on the cache. But it's likely to come up at some
point.
Ticket: openedx/openedx-events#235
This is a just-in-case measure -- we don't know of any specific code that
handles events and relies on the cache. But it's likely to come up at some
point.
Ticket: openedx/openedx-events#235
A/C:
Notes:
The RequestCache should be cleared between processing of each message to treat message processing like a request. In case any code is shared between message processing and the service itself, the RequestCache should have a common interpretation. Basically, we will be replacing this call that is currently in the RequestCacheMiddleware.
Note that for now the only cache between messages would be the shared Django cache (e.g. Memcached). We do not support a consumer level cache, and will leave that for when and if it becomes a priority.
The text was updated successfully, but these errors were encountered: