[
https://issues.apache.org/jira/browse/PROTON-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
NS-SlaFleur updated PROTON-2402:
--------------------------------
Description:
The Python documentation does not state the following explicitely which caused
some confusion on my end:
- on_settled is triggered on the disposition settled on remote side
- Container & other proton datastructures are NOT thread safe, use injector
for external thread communication
- on_sendable is called on each received flow event & after send if there are
still credits available.
PR: https://github.com/apache/qpid-proton/pull/324
was:
The Python documentation does not state the following explicitely which caused
some confusion on my end:
- on_settled is triggered on the disposition settled on remote side
- Container & other proton datastructures are NOT thread safe, use injector for
external thread communication
- on_sendable is called on each received flow event & after send if there are
still credits available.
> Clarify proton python documentation on thread-safeness and when certain
> callbacks are called
> --------------------------------------------------------------------------------------------
>
> Key: PROTON-2402
> URL: https://issues.apache.org/jira/browse/PROTON-2402
> Project: Qpid Proton
> Issue Type: Bug
> Components: python-binding
> Affects Versions: proton-c-0.34.0
> Reporter: NS-SlaFleur
> Priority: Minor
>
> The Python documentation does not state the following explicitely which
> caused some confusion on my end:
> - on_settled is triggered on the disposition settled on remote side
> - Container & other proton datastructures are NOT thread safe, use injector
> for external thread communication
> - on_sendable is called on each received flow event & after send if there
> are still credits available.
>
> PR: https://github.com/apache/qpid-proton/pull/324
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
