On Tue, Feb 09, 2010 at 10:07:14PM -0700, Neal Richter wrote:
> I realize its a non-load balacer use and agree with the inherent issue
> you point-out. Yet there are few pieces of software as capable at
> handling concurrent connections to disparate destinations with low
> overhead as haproxy.
>
> Many seeming solutions to the problem described are resource hogs
> and/or very leaky with resources.
>
> Seems as though there is enough raw material in haproxy's code to
> consider reusing parts of it..
but anyway as I explained, the application which will perform those requests will have to process all the responses, so by trying to do that in a proxy, you're just putting a constraint on an additional layer which should not be needed at all.
Willy Received on 2010/02/10 06:41
This archive was generated by hypermail 2.2.0 : 2010/02/10 06:45 CET