Help on designing using multiple location/upstream modules

[Reetesh Ranjan]

Hi!

> Date: Sat, 30 Nov 2013 14:37:04 -0800
> Subject: Re: Help on designing using multiple location/upstream modules
> From: agentzh at gmail.com
> To: nginx-devel at nginx.org
> 
> Hello!
> 
> On Sat, Nov 30, 2013 at 11:05 AM, Reetesh Ranjan wrote:
> > Thanks for the help! Going by the documentation of the lua-nginx-module on
> > its subrequest handling it looks really promising for my use case.
> 
> Great :)
> 
> > I am
> > currently writing the Sphinx2 upstream module.
> 
> BTW, you could also build a lua-resty-sphinx2 library atop ngx_lua's
> nonblocking cosocket API instead of writing an upstream C module. You
> can check out the lua-resty-mysql or lua-resty-redis libraries for
> examples:
> 
>     https://github.com/agentzh/lua-resty-mysql
> 
>     https://github.com/agentzh/lua-resty-redis
> 
> The ngx_lua cosocket API is more flexible and much easier to use :)
> That way you also don't have to use nginx subrequests at all ;)

I was already midway writing the upstream module, and completed it. It was a great exercise anyway for looking into guts of nginx upstream state machine. :) I would look at the lua ones next. I am sure the learning obtained here and the eventual approach I had to take would be useful to build lua-resty-sphinx2.
Looking forward to be part of the great openresty bundle! :)

> > Would get back with questions
> > in case I have any on using the lua-nginx-module for achieving what I need
> > to do.
> >
> 
> You're recommended to post ngx_lua related questions to the
> openresty-en mailing list:
> 
>     https://groups.google.com/group/openresty-en
> 
> That way we can see your mails sooner rather later :)
> 
> Best regards,
> -agentzh
> 
> _______________________________________________
> nginx-devel mailing list
> nginx-devel at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx-devel
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx-devel/attachments/20131205/7869847f/attachment-0001.html>