Pointers on writing an Nginx module/application which needs to talk to multiple backends (sometimes sequentially, sometimes parallel) to serve a single request

Ashish S ashishs.dev at gmail.com
Fri Mar 9 02:26:57 UTC 2012

Thank you Piotr.  Agentzh's fork of eval module works for me.

I am now trying to implement #2 - #6 now.   Are there sample 3rd party
modules which parallely talk to postgres and some other backend
service (rather, more than one backend services in parallel), then
merge results from the two, followed by an upstream call to another
backend service?


On Thu, Mar 8, 2012 at 5:30 AM, Piotr Sikora <piotr.sikora at frickle.com> wrote:
> Hi,
>> but figured that eval does
>> an in-memory subrequest, while Piotr's postgres module above doesn't
>> support in-memory subrequest.  Has anyone modified postgres module
>> code to work with in-memory sub-requests?
> agentzh forked eval module and made it work with regular subrequests (so
> also with ngx_postgres):
> https://github.com/agentzh/nginx-eval-module
> Alternatively, you could use ngx.location.capture() feature from ngx_lua
> module to make the subrequests to PostgreSQL location.
> I also believe that the first test case from
> https://github.com/FRiCKLE/ngx_postgres/blob/master/t/eval.t might be of
> interest to you.
> Best regards,
> Piotr Sikora < piotr.sikora at frickle.com >
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

More information about the nginx mailing list