Hello,
I guess that if you want to modify this, you need to make it optional.
The TCPNODELAY flag is related to the Nagle's algorithm
This algorithm is made to avoid sending very small paquets each time you
send data through your socket but instead wait 400ms (generally) or a full
buffer (or a message from the other side if I remember well) and send a
paquet that wrap more data. Thus, it tends to minimize the amount of small
data that are sent.
I am not familiar with JBossMQ code base but if you think that the
implementation could, at some time, send many small messages and would
suffer from sending each time a paquet, then you should most probably make
this setting optional. But, on the opposite, if you think that your paquet
(*all* paquets, even ACK) always have a sufficient size and don't want Nagle
to take care of you, then it is up to you.
Cheers,
Sacha
> -----Message d'origine-----
> De : [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]De la part de
> Hiram Chirino
> Envoy� : mercredi, 16 janvier 2002 04:17
> � : [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Objet : Re: [JBoss-dev] jbossmq message transport times
>
>
>
> I can't think of a reason that it would break anything...
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
