specify multiple urls in lua-resty-http or similar

aashish.aadhav

Hi !! ,

I would like to know if I can simulate multi curl using

lua-resty-http or similar modules.

aashish.aadhav · 2014-08-19T22:47:47+00:00

Hello,I think you should open a new connection for each new request:local red =require ("resty.redis"):new()red:set_timeout(100)local ok, err = red:co...

I think they accept only one url at one time. Is it true ?

Thanks for your time ,

--AshishA

manchev

You should really look at the docs before posting, it's all there already:

https://github.com/openresty/lua-nginx-module#ngxlocationcapture_multi
https://github.com/pintsized/lua-resty-http/#request_pipeline

Best,

Vladislav

On Tue, Aug 19, 2014 at 5:47 PM, ashish adhav <aashis...@gmail.com> wrote:

Hi !! ,

I would like to know if I can simulate multi curl using
lua-resty-http or similar modules.

I think they accept only one url at one time. Is it true ?

Thanks for your time ,
--AshishA

.

james_9172

Hi Ashish,

Yes, I agree please check the docs before posting, as you'll see the options available.

However I would add that multi curl isn't necessarily pipelining, IIRC. I believe curl has an option to run concurrent sub connections to arbitrary hosts, whereas pipelining requires the use of a single connection to a single host, for multiple ordered responses.

You could use the ngx.timer.at API to create multiple "light threads", which each create a lua-resty-http connection. This combined with connection pooling would be a good way to "concurrently" make upstream requests, scheduled by Nginx.

James.

On 19 August 2014 16:29, Vladislav Manchev <man...@bin.bz> wrote:

You should really look at the docs before posting, it's all there already:

https://github.com/openresty/lua-nginx-module#ngxlocationcapture_multi
https://github.com/pintsized/lua-resty-http/#request_pipeline

Best,
Vladislav

On Tue, Aug 19, 2014 at 5:47 PM, ashish adhav <aashis...@gmail.com> wrote:

Hi !! ,

I would like to know if I can simulate multi curl using
lua-resty-http or similar modules.

I think they accept only one url at one time. Is it true ?

Thanks for your time ,
--AshishA

.

--
James Hurst

ja...@pintsized.co.uk

agentzh

Hello!

On Tue, Aug 19, 2014 at 9:00 AM, James Hurst wrote:
> You could use the ngx.timer.at API to create multiple "light threads", which
> each create a lua-resty-http connection. This combined with connection
> pooling would be a good way to "concurrently" make upstream requests,
> scheduled by Nginx.
>

No, it's not recommended to use ngx.timer.at() in this context because
it'll be hard to "wait" on the threads if desired and also more
expensive. For this very use case, one should just use the ngx.thread
API to spawn more "light threads" directly, like ngx.thread.spawn().

Regards,
-agentzh

james_9172

Ah, sorry yes, that's what I meant ;)

On 19 August 2014 20:38, Yichun Zhang (agentzh) <age...@gmail.com> wrote:

Hello!

On Tue, Aug 19, 2014 at 9:00 AM, James Hurst wrote:
> You could use the ngx.timer.at API to create multiple "light threads", which
> each create a lua-resty-http connection. This combined with connection
> pooling would be a good way to "concurrently" make upstream requests,
> scheduled by Nginx.
>

No, it's not recommended to use ngx.timer.at() in this context because
it'll be hard to "wait" on the threads if desired and also more
expensive. For this very use case, one should just use the ngx.thread
API to spawn more "light threads" directly, like ngx.thread.spawn().

Regards,
-agentzh

.

--
James Hurst

ja...@pintsized.co.uk