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

Alan Conway commented on PROTON-1450:
-------------------------------------

Apologies for long delay: you are correct that filters apply only to the 
source. The proton C libary abstracts source and target as "terminus" but that 
includes everything from source and target, so I think the Go electorn package 
should follow the spec rather than the C library.

I prefer an AnnotationKey type because the same restricted type is used in  a 
few places in the spec.  Doing it as a type allows all the encode/decode rules 
to be handled in one place, and lets you store/pass AnnotationKey's around in 
your application without "forgetting" the restrictions. I'll take a stab at 
coding it up.

> Add Filter LinkOption to Electron API
> -------------------------------------
>
>                 Key: PROTON-1450
>                 URL: https://issues.apache.org/jira/browse/PROTON-1450
>             Project: Qpid Proton
>          Issue Type: Improvement
>          Components: go-binding
>            Reporter: Kale Blankenship
>            Assignee: Alan Conway
>
> There doesn't appear to be a way to set filters with the current Go bindings. 
> Microsoft's Event Hubs use filters to indicate the starting offset of 
> messages 
> (http://azure.github.io/amqpnetlite/articles/azure_eventhubs.html#filter). 
> Without this option it would be difficult to properly use the bindings with 
> Event Hubs.
> There is a wrapper which patches the bindings to provide the functionality 
> here: https://github.com/recobe182/gohub. Though I am not familiar enough 
> with Qpid to determine if the patch is reasonable.
> Thank you for considering this request and creating/maintaining this project!



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to