use it. However if such
AuthConfigProvider is not available, on every request we will spend
time in
redundant search operation to find AuthConfigProvider that is not
available.
What do you think about moving AuthConfigProvider initialization while
constructing the authenticator?
Won't
initialize it once and then we will use it. However if such
>>> AuthConfigProvider is not available, on every request we will spend time
> in
>>> redundant search operation to find AuthConfigProvider that is not
> available.
>>>
>>> What do you think about moving
ider we will
> >> initialize it once and then we will use it. However if such
> >> AuthConfigProvider is not available, on every request we will spend
time in
> >> redundant search operation to find AuthConfigProvider that is not
available.
> >>
> >> W
ider is not available, on every request we will spend time
in
>> redundant search operation to find AuthConfigProvider that is not
available.
>>
>> What do you think about moving AuthConfigProvider initialization while
>> constructing the authenticator?
>
>
> Won&#
AuthConfigProvider that is not available.
What do you think about moving AuthConfigProvider initialization while
constructing the authenticator?
Won't that break web applications that initialize their own JASPIC
configuration on web application start?
If performance is a concern we could st
you think about moving AuthConfigProvider initialization while
constructing the authenticator?
Thanks,
Violeta
