On 6/24/10 12:02 PM, Alexander Christian wrote:
On Thu, 24 Jun 2010 10:25:20 +0200, Emmanuel Lecharny
<[email protected]>
wrote:
But this fix isn't complete, or? If I now set the read buffer size with
the session config object, it's simply stored in the member variable,
but
not passed to the socket.
I checked this point, and I can confirm that the buffer size is
correctly read and passed to the socket.
So false alarm, pfewww...
But where? I checked out the complete source (1hr ago) and had a look into
You *have* to fix the value if you want it to be something that fits
your need. If not, the socket buffer size won't be set, as we check that
the config value has changed before setting it.
In any case, if the -1 value were to be used to set the socket buffer
size, an IllegalParameterException would have been thrown.
So here are the use cases :
- you don't set any value : the OS value will be used as we don't apply
the -1 value
- you have set a value in the SessionConfig : it will be used when the
session is created
What you can do is to get the underlying socket buffers size and print
them out to see that the OS value is in fact used in your tests.
--
Regards,
Cordialement,
Emmanuel Lécharny
www.nextury.com
