[
https://issues.apache.org/jira/browse/PROTON-2873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18046494#comment-18046494
]
ASF subversion and git services commented on PROTON-2873:
---------------------------------------------------------
Commit 32bcfccbd295bf576c8b5e02ed50afb8d6fbb7a1 in qpid-proton's branch
refs/heads/main from Andrew Stitcher
[ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=32bcfccbd ]
PROTON-2873: [Python] Remove caching for delivery remote disposition
We can't cache the remote disposition because it might be updated by the
remote peer, but we have no way to know it has been changed in the
delivery to invalidate the cache entry.
> Reorganize delivery disposition API and representation
> ------------------------------------------------------
>
> Key: PROTON-2873
> URL: https://issues.apache.org/jira/browse/PROTON-2873
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
> Affects Versions: proton-c-0.40.0
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Priority: Major
> Fix For: proton-c-0.41.0
>
>
> The internal representation and modelling for delivery dispositions is
> significantly different from the model of dispositions in the AMQP spec.
> One case in point causes the disposition representation to use more space
> than necessary as every field in every possible type of disposition is
> present. A better representation would be a union of the different
> disposistion types so that only the needed fields of whichever specific type
> of disposition is being used is present.
> For the present this would need to be additional APIs to maintain backwards
> compatibility. But the current disposition API should be deprecated and could
> be removed for a 1.0 release.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
