I'm not sure this is a bug per/se as opposed to a combination of
missunderstood and/or ill conceived features. The ~/ prefix when used in a
reply-to gets substituted with the name of the messenger. That is what is
substituting the container name into the address. The container name when
the messen
[
https://issues.apache.org/jira/browse/PROTON-491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-491:
-
Attachment: 01_append_topic_to_receiver_link_name.patch
Small patch to append the topic name to a
Dominic Evans created PROTON-571:
Summary: proton-c: Messenger outputs errors to stderr rather than
setting messenger->error
Key: PROTON-571
URL: https://issues.apache.org/jira/browse/PROTON-571
Proje
[
https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-571:
-
Attachment: 03_set_pn_error_when_printing_connection_errors.patch
Small patch to set messenger->e
Dominic Evans created PROTON-572:
Summary: proton-c: Messenger interprets a '#' topic to actually be
a request for a dynamic link
Key: PROTON-572
URL: https://issues.apache.org/jira/browse/PROTON-572
[
https://issues.apache.org/jira/browse/PROTON-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-572:
-
Attachment: 05_remove_messenger_request_dynamic_via_hash.patch
Patch to remove dynamic link behav
Dominic Evans created PROTON-573:
Summary: proton-c: Messenger appears to have hard-coded address
limits of 1024
Key: PROTON-573
URL: https://issues.apache.org/jira/browse/PROTON-573
Project: Qpid Pro
[
https://issues.apache.org/jira/browse/PROTON-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-573:
-
Attachment: 07_arbitrary_length_addresses_in_messenger.patch
06_arbitrary_length_a
Dominic Evans created PROTON-574:
Summary: proton-c: Messenger doesn't indicate when connection is
aborted for a SASL negotation failure
Key: PROTON-574
URL: https://issues.apache.org/jira/browse/PROTON-574
[
https://issues.apache.org/jira/browse/PROTON-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-574:
-
Attachment: 08_return_sasl_auth_errors_transport.h.patch
08_return_sasl_auth_error
Dominic Evans created PROTON-575:
Summary: proton-j: LoggingProtocolTracer used by FrameWriter
cannot be overridden
Key: PROTON-575
URL: https://issues.apache.org/jira/browse/PROTON-575
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-575:
-
Attachment: 01_allow_access_to_protocolTracer_in_TransportImpl.patch
Currently, we're just using
Dominic Evans created PROTON-576:
Summary: proton-j: codec support for UTF-8 encoding and decoding
appears broken?
Key: PROTON-576
URL: https://issues.apache.org/jira/browse/PROTON-576
Project: Qpid P
- Original Message -
> From: "Rafael Schloming"
> To: proton@qpid.apache.org
> Sent: Thursday, May 1, 2014 9:29:56 AM
> Subject: Re: Messenger.receive(1) causing sluggish behavior
>
> I'm not sure this is a bug per/se as opposed to a combination of
> missunderstood and/or ill conceived
[
https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-576:
-
Attachment: 02_fix_stringtype_encode_decode.patch
I'm not sure why the code was originally writte
[
https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=1398#comment-1398
]
clebert suconic commented on PROTON-576:
getBytes("UTF-8") is a very slow operatio
[
https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986753#comment-13986753
]
Dominic Evans commented on PROTON-576:
--
Whilst I think that was certainly true in Jav
[
https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986753#comment-13986753
]
Dominic Evans edited comment on PROTON-576 at 5/1/14 5:30 PM:
--
[
https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986807#comment-13986807
]
clebert suconic commented on PROTON-576:
Sounds a good idea.
Talking about micro
[
https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986890#comment-13986890
]
Dominic Evans commented on PROTON-576:
--
{code:title=results|borderStyle=solid}
Benchm
[
https://issues.apache.org/jira/browse/PROTON-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986910#comment-13986910
]
ASF subversion and git services commented on PROTON-495:
Commit 15
[
https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986911#comment-13986911
]
clebert suconic commented on PROTON-576:
200 samples is a small number. you should
Just a heads up, I've committed this to trunk. Please let me know if it
causes any problems.
--Rafael
On Tue, Apr 29, 2014 at 2:57 PM, Rafael Schloming wrote:
> Hi Everyone,
>
> I've put together a patch that makes the proton-j factory usage a bit
> simpler and more consistent. You can review
[
https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986913#comment-13986913
]
clebert suconic commented on PROTON-576:
why don't you share your test here?
> pr
[
https://issues.apache.org/jira/browse/PROTON-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved PROTON-495.
Resolution: Fixed
Assignee: Rafael H. Schloming
> fix proton constructors to
On Thu, May 01, 2014 at 09:29:56AM -0400, Rafael Schloming wrote:
> (and many others) you don't really even need more than one address. If you
> modify your example to just use "~/replies", it will work properly
> regardless of what value you pass to recv.
I did this, set the Messenger back to re
On Thu, May 01, 2014 at 04:02:51PM -0400, Darryl L. Pierce wrote:
> On Thu, May 01, 2014 at 09:29:56AM -0400, Rafael Schloming wrote:
>
> > (and many others) you don't really even need more than one address. If you
> > modify your example to just use "~/replies", it will work properly
> > regardle
[
https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-576:
-
Attachment: benchmark-src.zip
benchmark.jar
Benchmark jar (and src) as requested.
Hi Clebert,
I've been (amongst other things) doing a little bit of investigation on
this topic over the past couple of days. I wrote a microbenchmark that
takes two engines and directly wires their transports together. It then
pumps about 10 million 1K messages from one engine to the other. I ran
For now I have pretty much optimized the Transfer type only. no other types.
for instance I see that Disposition type needs optimization as well...
For us though the biggest advantage on the patch I'm making .
If you send a 1K message.. you won't have much of the optimization on the codec
bein
Ah... I will fix the license headers shortly.
On May 1, 2014, at 4:51 PM, Clebert Suconic wrote:
> For now I have pretty much optimized the Transfer type only. no other types.
>
> for instance I see that Disposition type needs optimization as well...
>
> For us though the biggest advantage
As no mail arrived here or qpid-dev, and none seems to have arrived at what
used to be the default location (infra-dev) either, I had a quick look and
it seems like they might have changed the process slightly and we will need
to ask for the mails to be enabled at all:
https://blogs.apache.org/infr
I will do some cleanup on this .. I already fixed the headers here on my copy
and I will do some cleanup on imports that were't supposed to be done.
On May 1, 2014, at 5:11 PM, Robbie Gemmell wrote:
> As no mail arrived here or qpid-dev, and none seems to have arrived at what
> used to be the de
33 matches
Mail list logo
