regardless of whether the context object is a dict or a class or a modified WSGI environ:
Does the idea of doing authorization at the data layer by checking against this variable (and hence always passing it in) seem like a good idea?
Right now many of the RS API and workers use either {} or None...
We would have to change all of these... (so regardless of what the context variable is, we need to send it to the workers when we do work)
regardless of whether the context object is a dict or a class or a modified WSGI environ:
Does the idea of doing authorization at the data layer by checking against this variable (and hence always passing it in) seem like a good idea?
Right now many of the RS API and workers use either {} or None...
We would have to change all of these... (so regardless of what the context variable is, we need to send it to the workers when we do work)