It's very nice indeed that SOAP 2.3 has direct API support for setting the TcpNoDelay option. It seems curious to me, though, that it's not defaulted to true (which, in the strange lingo of this option, means "yes, I want no delay"). I don't imagine any SOAP calls would ever benefit from having the Nagle algorithm delay.
Shouldn't we just default it to true instead of depending on callers to be wise enough to do it on their own? Just like in the stock market, where theinsiders will always have better performance than people like me, Apache SOAP insiders will know to call SOAPHttpConnection.setTcpNoDelay(BooleanTRUE) and have better performance than the unwashed. -- [EMAIL PROTECTED] (WJCarpenter) PGP 0x91865119 38 95 1B 69 C9 C6 3D 25 73 46 32 04 69 D6 ED F3 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
