This depends. The ServerIron is going to create a 1-to-1 mapping by
default. There is a single backend connection for all incoming
connection by default. I assume you are talking about a current
ServerIron modeul and not somethine like the ServerIron XL (10 years
old or even older). There is a feature called TCP offlad to allow
backend connections to stay open - multiple clients might use the
same backend connection doing so. The ServerIron is going to create
the first connection at the time the first request needs to get
forrwarded to a given real server. The client is going to close the
connection and the ServerIron keeps the backend connection open but
closes the frontend connection.
Have a look at TCP offload in the documentation - I guess that is
what you need based on your question.
Oliver
At 13:53 21.07.2009, Nagendra Modadugu wrote:
I have a proxy that would like to multiplex requests from multiple
clients over the same TCP connection (by relying on HTTP 1.1
keep-alive, but not pipelining requests). In general the requests
may be from different browsers, so the user agent strings will be
different -- does this situation pose a problem for ServerIron
configurations that switch to different backends based on
user-agent? Or rather, does ServerIron assume a 1:1 connection
mapping between frontend and backend connections?
Please let me know if I can clarify my question. Thanks,
- nagendra
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________
foundry-nsp mailing list
[email protected]
http://puck.nether.net/mailman/listinfo/foundry-nsp
