GitHub user mastash3ff opened a pull request:

    https://github.com/apache/qpid-proton/pull/103

    PROTON-1463 GO-Bindings Added AMQP Address Method

    Original examples used url.Path variable to return the amqp address.  The 
address returned added an unnecessary prepended slash character.  Added a 
amqp.Address() method to filter the slash character out.  
    
    Original problem running example:  ./receiver.go localhost:5672/example
    Receiver listened on the '/example' address instead of 'example'
    
    Also adjusted the receiver and sender examples to use url.Address() instead 
of passing url.Path.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mastash3ff/qpid-proton amqpAddressMethod

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/qpid-proton/pull/103.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #103
    
----
commit 1c246239789e91666353dd604ce64ce7b368eca3
Author: Brandon Sheffield <brandon>
Date:   2017-04-19T16:50:24Z

    Added Address() function to return an AMQP address.  Previous 
implementation relied on URL.Path to
    get an AMQP address.  This had the unintended consequence of returning 
addresses with '/' prepended.

commit 7b140d83786b7ed5ee3122a819e7f17f571143a0
Author: Brandon Sheffield <brandon>
Date:   2017-04-19T16:55:43Z

    adjusted Receivers to take address string instead of url.Path string that 
added an unnecessary slash character to address

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to