On 06/09/2011 03:48 PM, [email protected] wrote:
On 6/9/2011 6:37 AM, Gordon Sim wrote:
I would also echo Ted's comments, that the messaging API is really
what we recommend, and that the swigged version when completed
would be a drop in replacement for that (avoiding annoyances like
the above).
I agree that it should be a drop-in replacement, and I'm willing to
help make the necessary changes, but I don't see where. In the 0.10
release, there's the python package,
qpidc-0.10/bindings/qpid/python/cqpid.py, that would need to be
patched, but I don't see that in the repository.
It's generated by swig.
Where would the changes need to go?
I believe that the swig generation process can be customised to a
degree. However I suspect that would not be sufficient to be a drop in
replacement and that therefore some adapter layer would be required.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
