The engine examples in python currently use a special send_msg() method
that is dynamically added to the sender objects created by the
'container'. I never really liked this mechanism, it was just a short
term workaround to get the simplicity I wanted to expose without
requiring changes to the engine itself.
That was useful when still on a branch, but now I'd like to see if we
can find a better approach that keeps the simplicity I'm looking for,
the flexibility already present in the engine api and is more intuitive
and usable all round.
I've proposed a change here: https://reviews.apache.org/r/30318/
That just focuses on the change to the engine. If accepted, the examples
would all also change to use send() instead of send_msg(). Though on the
face a simple change this would actually be a bigger improvement under
the covers and would allow the same method to be used for sending
messages over links established by the peer also.
Comments welcome here or on the reviewboard.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org
