Re: [squid-users] Squid 3.5 with nonblocking ecap adapter

2017-11-01 Thread Alex Rousskov
On 11/01/2017 11:45 AM, Yuri wrote: > 01.11.2017 23:37, Alex Rousskov пишет: B) Use threads inside the adapter to make its operations asynchronous. >>> AFAIK B) is impossible. >> It is not only possible but implemented in sample and production >> adapters (as I have said later in the same em

Re: [squid-users] Squid 3.5 with nonblocking ecap adapter

2017-11-01 Thread Yuri
01.11.2017 23:37, Alex Rousskov пишет: > On 11/01/2017 09:26 AM, Yuri wrote: Is there a way other than programming the eCAP adapter in asynchronous mode? >>> I do not think there is a better alternative. AFAICT, you only have two >>> options: >>> >>> A) Change Squid to move eCAP calls

Re: [squid-users] Squid 3.5 with nonblocking ecap adapter

2017-11-01 Thread Alex Rousskov
On 11/01/2017 09:26 AM, Yuri wrote: >>> Is there a way other than >>> programming the eCAP adapter in asynchronous mode? >> I do not think there is a better alternative. AFAICT, you only have two >> options: >> >> A) Change Squid to move eCAP calls to thread(s). >> B) Use threads inside the ad

Re: [squid-users] Squid 3.5 with nonblocking ecap adapter

2017-11-01 Thread Yuri
01.11.2017 21:23, Alex Rousskov пишет: > On 11/01/2017 03:20 AM, Christof Gerber wrote: > >> [Will Squid] be blocked until the eCAP API call returns? > To answer the exact question above: Yes, the Squid worker making an eCAP > API call will block until that call returns. The same is true for all

Re: [squid-users] Squid 3.5 with nonblocking ecap adapter

2017-11-01 Thread Yuri
01.11.2017 21:23, Alex Rousskov пишет: > On 11/01/2017 03:20 AM, Christof Gerber wrote: > >> [Will Squid] be blocked until the eCAP API call returns? > To answer the exact question above: Yes, the Squid worker making an eCAP > API call will block until that call returns. The same is true for all

Re: [squid-users] Squid 3.5 with nonblocking ecap adapter

2017-11-01 Thread Yuri
01.11.2017 21:23, Alex Rousskov пишет: > On 11/01/2017 03:20 AM, Christof Gerber wrote: > >> [Will Squid] be blocked until the eCAP API call returns? > To answer the exact question above: Yes, the Squid worker making an eCAP > API call will block until that call returns. The same is true for all

Re: [squid-users] Squid 3.5 with nonblocking ecap adapter

2017-11-01 Thread Alex Rousskov
On 11/01/2017 03:20 AM, Christof Gerber wrote: > [Will Squid] be blocked until the eCAP API call returns? To answer the exact question above: Yes, the Squid worker making an eCAP API call will block until that call returns. The same is true for all other API calls, all system calls, and all inter

[squid-users] Squid 3.5 with nonblocking ecap adapter

2017-11-01 Thread Christof Gerber
Hi everyone I am working on an ecap adapter which attaches to Squid 3.5. The adapter is going to make an external socket call which results in an REST API call (lookup) which will cause a delay of some milliseconds until the response is available. As ecap is blocking I assume Squid will be blocke