[jira] [Commented] (PROTON-1138) Assorted C++ API cleanups

2016-03-21 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15205438#comment-15205438
 ] 

ASF subversion and git services commented on PROTON-1138:
-

Commit f2ae27d7e7a09c016a89be59e93d5796e01cc725 in qpid-proton's branch 
refs/heads/master from Clifford Jansen
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f2ae27d ]

PROTON-1138: handler options become link or connection options 
(https://reviews.apache.org/r/44927)


> Assorted C++ API cleanups
> -
>
> Key: PROTON-1138
> URL: https://issues.apache.org/jira/browse/PROTON-1138
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Affects Versions: 0.13.0
>Reporter: Justin Ross
>Assignee: Justin Ross
> Fix For: 0.13.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Created] (PROTON-1162) connection capabilities are not sent correctly by default

2016-03-21 Thread Gordon Sim (JIRA)
Gordon Sim created PROTON-1162:
--

 Summary: connection capabilities are not sent correctly by default
 Key: PROTON-1162
 URL: https://issues.apache.org/jira/browse/PROTON-1162
 Project: Qpid Proton
  Issue Type: Bug
  Components: python-binding
Affects Versions: 0.12.0
Reporter: Gordon Sim
Priority: Minor


The offered- or desired- capabilities on a connection, they are sent out 
incorrectly unless they are explicitly added as symbol or Array containing 
symbols.
E.g. instead of

{noformat}
conn.offered_capabilities=["foo", "bar"]
{noformat}

you must use:

{noformat}
conn.offered_capabilities=Array(UNDESCRIBED, Data.SYMBOL, symbol("foo"), 
symbol("bar"))
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-1159) [C++ binding] Improvements and updates necessary for qpid-interop-test

2016-03-21 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204993#comment-15204993
 ] 

ASF subversion and git services commented on PROTON-1159:
-

Commit 9e2649ac4f4996bbd84c217761fb506569cfd2a8 in qpid-proton's branch 
refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=9e2649a ]

PROTON-1159: Fixed linage for proton::internal::print_hex()


> [C++ binding] Improvements and updates necessary for qpid-interop-test
> --
>
> Key: PROTON-1159
> URL: https://issues.apache.org/jira/browse/PROTON-1159
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> A number of changes, additions and improvements which simplify the use of the 
> binding on qpid-interop-test (an interop test for AMQP clients).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-1159) [C++ binding] Improvements and updates necessary for qpid-interop-test

2016-03-21 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204992#comment-15204992
 ] 

ASF subversion and git services commented on PROTON-1159:
-

Commit caf4f8a16c137b8bb16a6d1fdbe51b9042d33293 in qpid-proton's branch 
refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=caf4f8a ]

PROTON-1159: Some improvements for qpid-interop-test: Added operator<<() to 
byte_array and decimal classes. Fixed UUID print bug.


> [C++ binding] Improvements and updates necessary for qpid-interop-test
> --
>
> Key: PROTON-1159
> URL: https://issues.apache.org/jira/browse/PROTON-1159
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> A number of changes, additions and improvements which simplify the use of the 
> binding on qpid-interop-test (an interop test for AMQP clients).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (PROTON-1159) [C++ binding] Improvements and updates necessary for qpid-interop-test

2016-03-21 Thread ASF subversion and git services (JIRA)

[ 
https://issues.apache.org/jira/browse/PROTON-1159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204978#comment-15204978
 ] 

ASF subversion and git services commented on PROTON-1159:
-

Commit 1b1503c128e32f9e8c4bdca7e18980dd856d46ea in qpid-proton's branch 
refs/heads/kvdr-PROTON-1159 from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=1b1503c ]

PROTON-1159: Fixed linage for proton::internal::print_hex()


> [C++ binding] Improvements and updates necessary for qpid-interop-test
> --
>
> Key: PROTON-1159
> URL: https://issues.apache.org/jira/browse/PROTON-1159
> Project: Qpid Proton
>  Issue Type: Improvement
>  Components: cpp-binding
>Reporter: Kim van der Riet
>Assignee: Kim van der Riet
>
> A number of changes, additions and improvements which simplify the use of the 
> binding on qpid-interop-test (an interop test for AMQP clients).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Messenger: Request Reply - Fundamental questions?

2016-03-21 Thread Flores, Paul A.
At client.



Considering Messenger and have been asked to describe how a Messenger would 
handle request reply processing.



Fundamental question -> Can a Messenger "act" as both a Message Producer (send) 
and Consumer (receive) messages or is a Messenger limited to a single "role"?



Consider the following "flow":



Starting from the Requester role:



A Message is created with the reply-to property set with a generated reply-to 
queue

A Messenger is "set up" to send a message

A Messenger sends the message



So here is where my confusion begins with Messenger

Knowing that the Messenger is expecting a reply when does the a Messenger begin 
to "listen" for a reply?  After the message is settled or before?

How does a Messenger "listen" for a reply?  Is it enough to do  a "get" on the 
reply-to Address supplied with the message?



It is obvious that the questions are similar in nature for the Messenger that 
is in the role of responding to a request which is at the heart of the 
fundamental question; transitioning between the implied roles in a Request 
Reply scenario.



Last fundamental question is whether blocking is sufficient to emulate 
synchronous call behavior?



Thanks for any inputs, insight or comments!



Paul Flores