in the right
places??? The question is: how BIG should the buffer be???
Regards,
Hiram
From: Jeff Tulley [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] jbossmq message transport times
Date: Wed, 16 Jan 2002 10:03:23 -0700
Actually it is even a little more complicated than
I made two changes which I'll describe here. I haven't yet investigated the
mechanics of submitting patches.
The changes are both in the org.jboss.mq.il.oil package. Note there are analogous
places in the other il subpackages that may also need changing-- my current test
evidently doesn't
- Original Message -
From: Loren Rosen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, January 18, 2002 1:58 PM
Subject: Re: [JBoss-dev] jbossmq message transport times
I made two changes which I'll describe here. I haven't yet investigated
the
mechanics of submitting patches.
The changes
,
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
Den 2002-01-16 02:37:12 skrev Loren Rosen [EMAIL PROTECTED]:
I'm
testing on MacOS X, which for our purposes is just another Unix flavor
with an oddball GUI.
Hi hi hi I'm waiting for my PB TI to arrive... really longing for Unix with an
oddball GUI :)
/Lennart
hi,
On Wed, 2002-01-16 at 10:58, Sacha Labourey wrote:
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
true.
This algorithm is made to avoid sending very small paquets each time you
send data through your
Actually it is even a little more complicated than that. Nagle's
algorithm by itself would not cause such delays, but what happened is
that at the other end somebody (I forget who) came up with the idea of a
delayed ACK. Since an ACK is a small packet, and one ACK can
acknowledge receipt for
: [JBoss-dev] jbossmq message transport times
Date: Wed, 16 Jan 2002 10:03:23 -0700
Actually it is even a little more complicated than that. Nagle's
algorithm by itself would not cause such delays, but what happened is
that at the other end somebody (I forget who) came up with the idea of a
delayed
]
Subject: RE: [JBoss-dev] jbossmq message transport times
Date: Wed, 16 Jan 2002 10:03:23 -0700
Actually it is even a little more complicated than that. Nagle's
algorithm by itself would not cause such delays, but what happened is
that at the other end somebody (I forget who) came up with the idea
