[
https://issues.apache.org/jira/browse/QPID-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rafael H. Schloming resolved QPID-979.
--------------------------------------
Resolution: Fixed
These have all been addressed with the exception of the acking issue which is
partially addressed but could still be more convenient. I've opened QPID-1520
for that.
> Improvements for the python client API
> --------------------------------------
>
> Key: QPID-979
> URL: https://issues.apache.org/jira/browse/QPID-979
> Project: Qpid
> Issue Type: Improvement
> Components: Python Client
> Affects Versions: M3
> Reporter: Rajith Attapattu
> Assignee: Rafael H. Schloming
> Fix For: M4
>
>
> It would be good if we could have the following for the python client API.
> 1) UUID for python < 2.5,
> UUID module is only introduced from python 2.5
> When creating a session it would be nice if we had the convinience of using a
> UUID generator.
> Rafi suggested that we could have a uuid method in the qpid.datatypes that
> will use the uuid module if python version is >= 2.5 and if not we could
> generate a uuid based on the RFC for uuid.
> 2) convenience for getting to a specific header property,
> Currently retrieving the headers from the message is a bit awkward, so a
> convinience method is good to have.
> Perhpas have this following method (courtesy Gordon) in the message class?
> def getProperty(msg, name):
> for h in msg.headers:
> if hasattr(h, name): return getattr(h, name)
> return None
> 3) cumulative ack
> Currently I ack per message and in the old API we had a cumilative ack.
> It would be nice to have the same thing.
> Regards,
> Rajith
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
