On Sep 18, 2013, at 10:39 PM, JT Archie <jta...@gmail.com> wrote:
> Can I ask, why did you also chose not to use WSAPI or lua-resty-rack for the request/response handling?
I started this before resty-rack actually existed. I think WSAPi is horrible for openresty - but that's just my opinion.
resty-rack seems to do a lot of work at request time and I wanted to do as much work as possible at init time and do very little during the request phase. Been a while since I looked at resty-rack, so that may have changed.
> I've been trying to see if there is a way to consolidate a good middleware pattern. I think that its hard to do with OpenResty because you are provided with an object (ngx) that is basically request and response in one.
Yeah, that's why I "wrapped" ngx in request and response "objects"
> By the way, nice job. :)
Thanks.
Like I said, just something I was playing for a project I never finished. Most of my "day job work" is done in "raw" openresty rather than a framework as its generally extremely performance sensitive.