[Satosa-dev] sharing state between satosa microservices
12 Jul
2019
12 Jul
'19
7:56 a.m.
Am 2019-07-12 um 00:40 schrieb Giuseppe De Marco
<giuseppe.demarco at unical.it>:
I love it, you are talking about something like
from django.conf import settings
right, with the exception that django hides some flexibility in configuring the settings
file behind the import statement.
So you are looking for a way to have a request microservice configuration available to a
response microservice
OR
to a strategy to handle a session object to fill of whatever in in each moment (runtime),
like in Django we can do with request.session object (as context object propose in satosa)
Could we store all the proxy/plugins configuration in context object as a final solution?
Not exactly. I have to 3 use cases:
1) obtain the satosa configuration in a microservice (currently only the ms configuration
is available)
2) a potential refactoring that where modules would import configuration like in django,
instead of passing the config as constructor argument.
3) pass the request state from request ms to the response ms
The „singleton" pattern applies to 1 + 2, whereas I think the 3 is a separated
concern. But it would be nice to have both types of state sharing as a defined
infrastructure in satosa, not as a ms-specific hack.
- Rainer