Hi Alan,
-aconway acon...@redhat.com wrote: -
I don't see any pn_message_copy function in the proton library, is there an
efficient way to make an independent copy of a message? I can encode and
decode but that seems like a long way around.
I actually had a patch lying around to add
-aconway acon...@redhat.com wrote: -
Is this just because the go code isn't at the top-level?
Can't you just rename your current branch out of the way and then
subtree the binding and push it to the go1 branch?
e.g., something like...
# rename old full tree branch and push it
-aconway acon...@redhat.com wrote: -
I would like to create a separte git repo for the proton Go binding.
Go provides go get to grab online go source libraries, based on
cloning repos. The go tools assume that each go project has its own
repo. I have tried to make this work directly
I do have an unpushed change that partially enables it for travis. I'll
push later tonight.
On 8 Jul 2015, at 18:27, Ken Giusti kgiu...@redhat.com wrote:
Good point, I'll see what I can do on that front.
- Original Message -
From: Robbie Gemmell robbie.gemm...@gmail.com
To:
Dominic Evans created PROTON-931:
Summary: proton-j: unable to determine if LINK_REMOTE_DETACH
happened in response to a local detach
Key: PROTON-931
URL: https://issues.apache.org/jira/browse/PROTON-931
When we were implementing the MQ Light broker, we wanted to be able to support
sharing of subscriptions across a group of clients - in particular for the
worker offload scenario. At the time we were unable to find guidance in the
specification or extensions thereof, so we went ahead with
-Robbie Gemmell robbie.gemm...@gmail.com wrote: -
The Java test runs have apparently been failing since the last few
commits went in for the Go bits.
https://builds.apache.org/job/Qpid-proton-j/
I spotted this as it was also causing a `make install` to fail on the proton-c
jenkins.
-Robbie Gemmell robbie.gemm...@gmail.com wrote: -
There were some changes on master and the branch yesterday, so I have
updated the commit lists again. The current categorised list of
commits is now at:
http://people.apache.org/~robbie/qpid/proton/0.9.1/git-cherry-pass3-c
-Robbie Gemmell robbie.gemm...@gmail.com wrote: -
I have gone through the git cherry output and categorised the
remaining commits from master that dont have a direct equivalent on
the 0.9.x branch, splitting according to what they update i.e. mainly
by language. I listed some as
-Rafael Schloming r...@alum.mit.edu wrote: -
On Tue, Apr 14, 2015 at 1:27 PM, Alan Conway acon...@redhat.com
wrote:
That works for me, now how do we manage the transition? I don't think
we can afford to inflict yum update proton; all proton apps crash
on our users. That means we
[
https://issues.apache.org/jira/browse/PROTON-844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans resolved PROTON-844.
--
Resolution: Fixed
proton-j: ArrayIndexOutOfBounds exception if remote peer sends a handle 1024
Dominic Evans created PROTON-843:
Summary: proton-j: Transport advertises idle timeout as-is whereas
proton-c halves it before
Key: PROTON-843
URL: https://issues.apache.org/jira/browse/PROTON-843
Dominic Evans created PROTON-844:
Summary: proton-j: ArrayIndexOutOfBounds exception if remote peer
sends a handle 1024
Key: PROTON-844
URL: https://issues.apache.org/jira/browse/PROTON-844
Project
2.4.5 Idle Timeout Of A Connection
To avoid spurious timeouts, the value in idle-time-out SHOULD be half the
peer's actual timeout threshold
So, to me, this means on the @open performative the client should flow (e.g.,)
3 as the idleTimeOut it would like to negotiate, but should actually
-Rafael Schloming r...@alum.mit.edu wrote: -
On Wed, Apr 1, 2015 at 6:00 AM, Dominic Evans dominic.ev...@uk.ibm.com
wrote:
2.4.5 Idle Timeout Of A Connection
Thoughts?
I believe your interpretation is correct. I've certainly noticed idle frames
being sent significantly more
-Ken Giusti kgiu...@redhat.com wrote: -
I've gone back and forth about what the proper behavior should be for
Proton re: idle timeout.
It's that darn pesky SHOULD... which means 'recommended', not
exactly 'required'.
Yes, I was similarly surprised that the spec chose to say 'SHOULD'
[
https://issues.apache.org/jira/browse/PROTON-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans reopened PROTON-834:
--
Assignee: Dominic Evans
proton-j: UTF-8 encoder reporting some three byte characters
Hey Rafa,
I did already cherry pick it into the release branch.
Cheers
Dom
On 16 Mar 2015, at 18:54, Rafael Schloming r...@alum.mit.edu wrote:
I'm happy to do a quick turnaround on RC 3 if you/he wants to pull the
fix
onto the release branch.
--Rafael
On Tue, Mar 17, 2015 at 5:54 AM,
[
https://issues.apache.org/jira/browse/PROTON-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-834:
-
Fix Version/s: (was: 0.9)
proton-j: UTF-8 encoder reporting some three byte characters
Dominic Evans created PROTON-834:
Summary: proton-j: UTF-8 encoder reporting some three byte
characters as invalid surrogates
Key: PROTON-834
URL: https://issues.apache.org/jira/browse/PROTON-834
[
https://issues.apache.org/jira/browse/PROTON-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans resolved PROTON-834.
--
Resolution: Fixed
Pushed c65e897
proton-j: UTF-8 encoder reporting some three byte
Dominic Evans created PROTON-832:
Summary: messenger: next_drain is not reset for manual link
credit mode in messenger
Key: PROTON-832
URL: https://issues.apache.org/jira/browse/PROTON-832
Project
[
https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans resolved PROTON-548.
--
Resolution: Fixed
Just noticed that the windows fix was comitted by [~chug] under commit
[
https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans closed PROTON-548.
Proton-C driver and URL Parsers don't support AF_INET6 (IPv6
[
https://issues.apache.org/jira/browse/PROTON-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans reassigned PROTON-832:
Assignee: Dominic Evans
messenger: next_drain is not reset for manual link credit mode
[
https://issues.apache.org/jira/browse/PROTON-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans resolved PROTON-832.
--
Resolution: Fixed
messenger: next_drain is not reset for manual link credit mode in messenger
Hi Alan,
-Alan Conway acon...@redhat.com wrote: -
I plan to start working on a go golang.org binding for proton. I
envisage a SWIG binding similar to the other swig-based bindings
(python, ruby, etc.) and an API layer similar to the new reactive
Python API (based on the C reactor.)
http://golang.org/cmd/cgo/
:/
--
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU
Rafael Schloming r...@alum.mit.edu wrote on 16/02/2015 20:02:07:
On Mon, Feb 16, 2015 at 2:32 PM, Alan Conway acon...@redhat.com wrote:
I work on a mix of SVN and GIT-based projects so I switch between
trunk
and master a lot. Proton used to be an SVN based project. I repeatedly
stub my
In proton-c pn_sender / pn_receiver in the engine will always return a brand
new link.
But their equivalents in SessionImpl in proton-j, keep a cached list of the
existing session links, and return you one of those if you already have a
link with the name you asked for - which is pretty much what
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans resolved PROTON-154.
--
Resolution: Fixed
Fix Version/s: 0.9
proton-j: link attach, detach, attach sequence
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-154:
-
Summary: proton-j: link attach, detach, attach sequence on single session
does not result
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans reassigned PROTON-154:
Assignee: Dominic Evans
link attach, detach, attach sequence on single session does
[
https://issues.apache.org/jira/browse/PROTON-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14314293#comment-14314293
]
Dominic Evans commented on PROTON-154:
--
hit this issue on proton-j in HEAD, no longer
[
https://issues.apache.org/jira/browse/PROTON-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14309067#comment-14309067
]
Dominic Evans commented on PROTON-775:
--
[~mcpierce] do you have any thoughts of how
[
https://issues.apache.org/jira/browse/PROTON-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans reassigned PROTON-737:
Assignee: Dominic Evans (was: Darryl L. Pierce)
[PATCH] ruby: StateError not included
[
https://issues.apache.org/jira/browse/PROTON-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans closed PROTON-737.
[PATCH] ruby: StateError not included in exceptions
[
https://issues.apache.org/jira/browse/PROTON-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans resolved PROTON-814.
--
Resolution: Fixed
Fix Version/s: 0.9
proton-c: pn_selector_select caches its return
[
https://issues.apache.org/jira/browse/PROTON-814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans closed PROTON-814.
proton-c: pn_selector_select caches its return code from a previous error
[
https://issues.apache.org/jira/browse/PROTON-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans resolved PROTON-483.
--
Resolution: Fixed
I believe this is fixed by PROTON-677
detach with closed=false
[
https://issues.apache.org/jira/browse/PROTON-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans reassigned PROTON-483:
Assignee: Dominic Evans
detach with closed=false (or unspecified) not handled
Rafael Schloming-3 wrote
These projects aren't actually quite as independent as they look. There is
a common test suite that runs against both implementations to help keep
them in sync with each other. This is the python test suite that lives
underneath the top level tests/python directory.
Dominic Evans created PROTON-814:
Summary: proton-c: pn_selector_select caches its return code from
a previous error
Key: PROTON-814
URL: https://issues.apache.org/jira/browse/PROTON-814
Project
[
https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans reassigned PROTON-757:
Assignee: Dominic Evans
[PATCH] proton-c: transport errors are output to stderr in 0.8
[
https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans closed PROTON-757.
[PATCH] proton-c: transport errors are output to stderr in 0.8 onwards
[
https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans closed PROTON-751.
[PATCH] proton-c: pn_connect failures aren't exposed via messenger-error
[
https://issues.apache.org/jira/browse/PROTON-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans resolved PROTON-757.
--
Resolution: Fixed
Fix Version/s: 0.9
Pushed under 78e54ee
[PATCH] proton-c: transport
[
https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans reassigned PROTON-751:
Assignee: Dominic Evans
[PATCH] proton-c: pn_connect failures aren't exposed via
[
https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans resolved PROTON-751.
--
Resolution: Fixed
Fix Version/s: 0.9
fixed in b9423d4
[PATCH] proton-c: pn_connect
On 29 Jan 2015, at 04:00, Alan Conway acon...@redhat.com wrote:
The apache CI builds say I broke the proton build
https://builds.apache.org/job/Qpid-proton-c/492/consoleText
So of course I want to fix it. However the build output shows it never
even gets to running the tests. It looks
xavier wrote
Perhaps I must free some object, but in debug mode and checking the
memory, memory grow up, each time I do pn_messenger_subscribe,
pn_messenger_recv, etc.
did you try running your binary via valgrind memcheck?
--
View this message in context:
Dominic Evans created PROTON-775:
Summary: ruby: message annotations send from a ruby client are
invalid
Key: PROTON-775
URL: https://issues.apache.org/jira/browse/PROTON-775
Project: Qpid Proton
Dominic Evans created PROTON-776:
Summary: proton-j: Message.decode doesn't validate all data types?
Key: PROTON-776
URL: https://issues.apache.org/jira/browse/PROTON-776
Project: Qpid Proton
Hi Xavier, so 006FE360 is your messenger that is responsible for subscribing
and receiving the messages based upon the selector.
xavier wrote
[006FE360]: - SASL
[006FE360]:0 - @sasl-init(65) [mechanism=:PLAIN,
initial-response=b\x00emc2\x00emc2]
[006FE360]: - SASL
[006FE360]:0 -
Hi Xavier,
xavier wrote
I posted my solution, it works, but I did some performance test, and it's
not very good, I found why. In my solution, I start, and stop for any
receiver the messenger, because if I don't do this, with my code (posted)
I receive one time, the message with a filter
Hi Michael,
Michael Goulish wrote
After getting complete data for a 10 gigamessage interbox test,
( proton-c, event interface, code here:
https://github.com/mick-goulish/proton_c_clients.git )
...I see that there is no gradual speed change at all over the duration of
the test.
I
[
https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-548:
-
Attachment: 08_fix_ipv6_windows.patch
patch rebased against 0.8
Proton-C driver and URL Parsers
[
https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-548:
-
Attachment: (was: 08_fix_ipv6_windows.patch)
Proton-C driver and URL Parsers don't support
[
https://issues.apache.org/jira/browse/PROTON-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-763:
-
Description:
As discussed on IRC. https://issues.apache.org/jira/browse/PROTON-677 (git
commit
On 29 Nov 2014, at 14:20, Fraser Adams fraser.ad...@blueyonder.co.uk
wrote:
Hopefully this is useful to people, it's been something of a labour of
love over the last year.
I'm looking forward to checking this out now it has dropped into master. It
was only when you recently posted on the
[
https://issues.apache.org/jira/browse/PROTON-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-758:
-
Description:
As discussed on IRC
When SASL negotiation fails (e.g., wrong type, bad user+pass
[
https://issues.apache.org/jira/browse/PROTON-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14223514#comment-14223514
]
Dominic Evans commented on PROTON-752:
--
[~mcpierce] so I had a look at the patch
Dominic Evans created PROTON-752:
Summary: Ruby: Cproton calls don't unlock the GIL for blocking /
long-running operations
Key: PROTON-752
URL: https://issues.apache.org/jira/browse/PROTON-752
Dominic Evans created PROTON-751:
Summary: [PATCH] proton-c: pn_connect failures aren't exposed via
messenger-error
Key: PROTON-751
URL: https://issues.apache.org/jira/browse/PROTON-751
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-751:
-
Attachment: 0001-If-pn_connect-fails-copy-io-error-to-messenger.patch
patch attached
[PATCH
[
https://issues.apache.org/jira/browse/PROTON-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-748:
-
Attachment: 0001-Add-support-for-Messenger-snd-rcv-modes-and-flags.patch
patch attached
[PATCH
[
https://issues.apache.org/jira/browse/PROTON-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-743:
-
Attachment: 0001-Wrapper-pn_error-so-user-has-more-control-over-it.patch
patch attached.
[PATCH
Few minor things I noticed:
1) the github.com/Apache/qpid-proton mirror has been deleted, but the
git.apache.org mirror remains? Intentional? The GitHub mirror is still
useful for tracking forks...
2) there doesn't appear to be any linkage between JIRAs and commits
anymore? Does someone need to
[
https://issues.apache.org/jira/browse/PROTON-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14200916#comment-14200916
]
Dominic Evans commented on PROTON-634:
--
[~kgiusti] it seems this has already been
Dominic Evans created PROTON-738:
Summary: Debian + Ubuntu Packages need updating to 0.8
Key: PROTON-738
URL: https://issues.apache.org/jira/browse/PROTON-738
Project: Qpid Proton
Issue Type
Dominic Evans created PROTON-736:
Summary: ruby: unable to send binary data?
Key: PROTON-736
URL: https://issues.apache.org/jira/browse/PROTON-736
Project: Qpid Proton
Issue Type: Bug
Dominic Evans created PROTON-737:
Summary: [PATCH] ruby: StateError not included in exceptions
Key: PROTON-737
URL: https://issues.apache.org/jira/browse/PROTON-737
Project: Qpid Proton
[
https://issues.apache.org/jira/browse/PROTON-737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-737:
-
Attachment: 42_add_missing_exception_to_ruby_bindings.patch
[PATCH] ruby: StateError
[
https://issues.apache.org/jira/browse/PROTON-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14196358#comment-14196358
]
Dominic Evans commented on PROTON-736:
--
[~mcpierce] as discussed on IRC
The problem
Rafael Schloming-3 wrote
I like the gradual migration concept. I do use git-blame / git-annotate
enough for a wholesale changeover to be problematic.
Is there an easy way to see what the actual diffs are so we have an idea
of
what the various format policies actually mean?
well installing
When using messenger in non-blocking mode, it is possible to ensure that the
empty frame heartbeats are sent by calling pn_messenger_work(timeout) on a
regular interval (when no other send / recv operations are happening).
However, when using messenger in blocking mode it is not obvious how one
Dominic Evans wrote
When using messenger in non-blocking mode, it is possible to ensure that
the empty frame heartbeats are sent by calling pn_messenger_work(timeout)
on a regular interval (when no other send / recv operations are
happening).
However, when using messenger in blocking mode
[
https://issues.apache.org/jira/browse/PROTON-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14182596#comment-14182596
]
Dominic Evans commented on PROTON-725:
--
[~E528527] this is what URL encoding
fadams wrote
On 08/10/14 18:49, Rafael Schloming wrote:
Actually I think it is possible to do this with messenger now that
dominic's patches are in. You can access the link associated with any
given
address using pn_messenger_get_link() and configure it however you want
to.
--Rafael
Oooh
Rafael Schloming-3 wrote
I've created 0.8 RC1 and posted it in the usual locations. The source can
be found here:
http://people.apache.org/~rhs/qpid-proton-0.8rc1/
I know it is a *very* minor issue, but just for tidyness could someone fix
PROTON-618 for 0.8 ?
--
View this message in
fadams wrote
And possibly PROTON-571 too?
See the thread proton Messenger error handling/recovery REQUEST
FEEDBACK! on the qpid user list, I *think* Dominic's patch should go
some way to improving that (is that correct Dominic?)
It does indeed. And PROTON-574 and PROTON-676 extend it to
For operations such as `pn_link_close` its fairly easy to confirm that it has
been transmitted over the network and that the appropriate @close response
has been received from the remote end by doing a state check (e.g., if
(!(pn_link_state(link) PN_REMOTE_CLOSED)) type thing)
I previously
[
https://issues.apache.org/jira/browse/PROTON-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-576:
-
Attachment: (was: 02_fix_stringtype_encode_decode.patch)
proton-j: codec support for UTF-8
[
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
Patch refreshed.
proton-j: codec support
[
https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-571:
-
Attachment: (was: 03_set_pn_error_when_printing_connection_errors.patch)
proton-c: Messenger
[
https://issues.apache.org/jira/browse/PROTON-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-574:
-
Attachment: (was: 08_return_sasl_auth_errors_transport.h.patch)
proton-c: Messenger doesn't
[
https://issues.apache.org/jira/browse/PROTON-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-574:
-
Attachment: (was: 08_return_sasl_auth_errors_messenger.c.patch)
proton-c: Messenger doesn't
[
https://issues.apache.org/jira/browse/PROTON-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-574:
-
Attachment: (was: 08_return_sasl_auth_errors_transport.c.patch)
proton-c: Messenger doesn't
Dominic Evans created PROTON-669:
Summary: proton-c: Messenger abstracts away connections, but it
would be useful to fail fast for auth errors etc.
Key: PROTON-669
URL: https://issues.apache.org/jira/browse
[
https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-548:
-
Attachment: (was: 14_fix_ipv6_windows.patch)
Proton-C driver and URL Parsers don't support
[
https://issues.apache.org/jira/browse/PROTON-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-548:
-
Attachment: 08_fix_ipv6_windows.patch
Proton-C driver and URL Parsers don't support AF_INET6
[
https://issues.apache.org/jira/browse/PROTON-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-669:
-
Attachment: 07_add_messenger_route_check_on_start_transform.h.patch
[
https://issues.apache.org/jira/browse/PROTON-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-578:
-
Attachment: 10_fix_winsock_error_code_printing.patch
proton-c: windows/io.c prints Unknown error
[
https://issues.apache.org/jira/browse/PROTON-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-578:
-
Attachment: (was: 17_fix_winsock_error_code_printing.patch)
proton-c: windows/io.c prints
[
https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-571:
-
Attachment: 02_set_pn_error_when_printing_connection_errors.patch
[
https://issues.apache.org/jira/browse/PROTON-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-571:
-
Attachment: (was: 02_set_pn_error_when_printing_connection_errors.patch)
proton-c: Messenger
Dominic Evans created PROTON-670:
Summary: proton-c: Messenger doesn't provide accessors for the
links it is using
Key: PROTON-670
URL: https://issues.apache.org/jira/browse/PROTON-670
Project: Qpid
[
https://issues.apache.org/jira/browse/PROTON-670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-670:
-
Attachment: 12_get_link_from_tracker_messenger.h.patch
[
https://issues.apache.org/jira/browse/PROTON-670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14129860#comment-14129860
]
Dominic Evans commented on PROTON-670:
--
patches attached to allow user to determine
[
https://issues.apache.org/jira/browse/PROTON-671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dominic Evans updated PROTON-671:
-
Attachment: (was:
13_add_pn_messenger_set_settle_mode_functions_to_header.patch)
proton-c
1 - 100 of 170 matches
Mail list logo
