On 09/28/2017 04:52 PM, Daniel Wagner wrote:
From: Bjoern Thorwirth
The calling process, that implements the session API is identified by
the user ID as it is runs. All processes of the same user share the
same list of allowed bearers, and the same priority for choosing
between available bearers.
This extension allows processes to select a service context dependent
behaviour for which the routing decision is made.
This is an extention to session API interface. Helps to enable a
service differentiation for processes run by the same user. Allows
ConnMan to differentiate between bearer usage permissions and the
respective priorities based on the requested service type.
after an offline discussion with Bjorn, we came to the conclusion that
my idea with AllowedServices is going into the wrong
direction. At least for his use case.
Propably I got confused by the name 'Session'. By calling this
ContextIdentifier we should avoid this confusion. In the end it is
just an additonal information given by the application to support the
bearer selection algorithm. Currently, the session code in ConnMan
doesn't make use of it, but a session plugin can use it. That is what
Patch applied. Happy hacking on your session plugin! Looking forward
when you release it :)