michael goulish created PROTON-296:
--
Summary: need a new message status
Key: PROTON-296
URL: https://issues.apache.org/jira/browse/PROTON-296
Project: Qpid Proton
Issue Type: Bug
C
michael goulish created PROTON-295:
--
Summary: recv(-1) + incoming_window == bad
Key: PROTON-295
URL: https://issues.apache.org/jira/browse/PROTON-295
Project: Qpid Proton
Issue Type: Bug
Hi,
I am new to proton/qpid, so I am not sure if I am doing this right or if
it is a general problem, maybe someone can point me into the right direction.
I was testing sending and receiving messages to the Azure service, I was
using the proton send and recv examples. It worked well, however ther
That's a good question and now that you mention it nothing prevents it.
That was an intentional choice when the feature was added, and it wasn't a
problem at the time because we didn't have recv(-1). This meant that you
were always asking for an explicit amount and if you asked for more than
your w
Ted Ross created PROTON-294:
---
Summary: Driver - Enable TCP_NODELAY on connections by default.
Key: PROTON-294
URL: https://issues.apache.org/jira/browse/PROTON-294
Project: Qpid Proton
Issue Type:
https://issues.apache.org/jira/browse/PROTON-294
On 03/15/2013 08:18 AM, Ted Ross wrote:
+1
It would be good to make this configurable, but in the absence of
configurability, we should turn Nagle off by default.
-Ted
On 03/14/2013 03:25 PM, Rafael Schloming wrote:
I think in most of the oth
( a question inspired by a question from a reviewer of
one of my docs... )
If you set an incoming message window of a certain size,
and if Messenger can receive messages even when you, i.e.
call send() - - - what's to stop some messages from
falling off the edge of that window, and thus gettin
