On 08/02/17 15:53, Violeta Georgieva wrote:
2017-02-07 23:54 GMT+02:00 Violeta Georgieva :
2017-02-07 23:44 GMT+02:00 Mark Thomas :
On 06/02/17 20:35, Violeta Georgieva wrote:
Hi,
With the current implementation if there is AuthConfigProvider we will
initialize it once and then we will u
On 07/02/17 21:54, Violeta Georgieva wrote:
> 2017-02-07 23:44 GMT+02:00 Mark Thomas :
>>
>> On 06/02/17 20:35, Violeta Georgieva wrote:
>>>
>>> Hi,
>>>
>>> With the current implementation if there is AuthConfigProvider we will
>>> initialize it once and then we will use it. However if such
>>> Aut
2017-02-07 23:54 GMT+02:00 Violeta Georgieva :
>
>
>
> 2017-02-07 23:44 GMT+02:00 Mark Thomas :
> >
> > On 06/02/17 20:35, Violeta Georgieva wrote:
> >>
> >> Hi,
> >>
> >> With the current implementation if there is AuthConfigProvider we will
> >> initialize it once and then we will use it. However
2017-02-07 23:44 GMT+02:00 Mark Thomas :
>
> On 06/02/17 20:35, Violeta Georgieva wrote:
>>
>> Hi,
>>
>> With the current implementation if there is AuthConfigProvider we will
>> initialize it once and then we will use it. However if such
>> AuthConfigProvider is not available, on every request we
On 06/02/17 20:35, Violeta Georgieva wrote:
Hi,
With the current implementation if there is AuthConfigProvider 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 AuthCo