----- "Rüdiger \"Plüm, VF-Group\"" <[email protected]> wrote:
> > -----Original Message----- > > From: Graham Leggett > > Sent: Freitag, 19. November 2010 12:19 > > To: [email protected] > > Subject: Re: svn commit: r1035605 - > > /httpd/httpd/trunk/modules/proxy/mod_proxy_http.c > > > > > > > bb is created like so: > > > > bb = apr_brigade_create(p, c->bucket_alloc); > > > > In other words, from the front side connection's allocator. > > When we've > > closed early, bb will be empty, which means this is a noop, but the > > brigade is guaranteed to still exist. > > Ahh, ok. Thanks for clarification. I believe to have, for the first time in months, understood what it is with mod_proxy, and why it's so heavily discussed: There are a number separate and related issues, because mod_proxy: * handles connections to the front end (To large numbers of differently behaving clients) * handles (highly configurable) connections to the back-end * can speak very different protocols to the back-ends (In terms of timeouts, keep-alives, etc..) * can be a transparent proxy as well as a reverse proxy * The code might, or might not be heavily interwoven. is that remotely right? > Regards > > Rüdiger i -- Igor Galić Tel: +43 (0) 664 886 22 883 Mail: [email protected] URL: http://brainsware.org/
