And one thing more.. I've read source of proxy_pass / memcached module to check how they use upstream. Unfortunately upstream servers are defined in nginx configure file. It's useless for us. We need to parse incoming buffers in filter, find server uri and download some content. Is there another way to configure upstream? During work of body_filter? In upstream.h there is only one function whby piotreek - Nginx Mailing List - English
Ok, we've written asynchronous resolver and it seems to work properly. However, we have problems with subrequests.. We thought about them at the very beginning, we tried to understand their mechanism by reading SSI filter source code, but it was really complicated, so we've written our own module to do that. For example - when I use subrequest in simplest way: ngx_http_myfilter_body_filteby piotreek - Nginx Mailing List - English
Many thanks for your comments! Ad 1. You're right. We changed the code style and now it should be consistent and similar to Nginx style. ;) Ad 2. This is interesting. We've thought about using an upstream, what is more, we've tried to do it. ;) However, our module allows to download simultaneously a lot of files, when upstream allows to download only one per one request. Am I wrong? Is it poby piotreek - Nginx Mailing List - English
Hi, We have written new Nginx modules and we publish them in hope of getting opinions. :) Generally, these modules are connected with XML and XSLT processing. Information and short description are available at http://xxslt.sourceforge.net I’m especially interested in review of XSLT2 module. It’s very similar to Igor Sysoev’s XSLT module, but allows to declare XSL style sheets directlyby piotreek - Nginx Mailing List - English