You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/11/18 20:49:11 UTC

[jira] [Commented] (PROTON-1047) go: improved ack handling in electron API, add to broker example

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

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

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

PROTON-1047: go: improved ack handling in electron API, add to broker example

Sender interface changed
- SendAsync: flexible and efficient server-side ack handling across multiple Senders.
- SendSync, SendForget, SendWaitable: easy-to-use methods for common client cases.

electron broker.go, send.go examples demonstrate async send handling.


> go: improved ack handling in electron API, add to  broker example
> -----------------------------------------------------------------
>
>                 Key: PROTON-1047
>                 URL: https://issues.apache.org/jira/browse/PROTON-1047
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: go-binding
>            Reporter: Alan Conway
>            Assignee: Alan Conway
>             Fix For: 0.12.0
>
>
> Presently every Send() call returns a SentMessage with a separate channel to notify on ack. This is ideal for simple clients but does not scale well in a broker where you need to monitor large numbers of acks efficiently.
> New scheme allows the user to supply the ack channel on send, so they can create a separate channel for individual acks or use a common channel for multiple acks.
> Update the broker example to illustrate this by keeping track of un-acknowledged messages till accept and re-queueing them on disconnect or reject.



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