On 07/11/2013 11:39 AM, Gordon Sim wrote:
On 07/11/2013 04:21 PM, Alan Conway wrote:
I'm not using the swigged bindings but I would vote for qpid.messaging
over qpid_messaging. I really dislike putting prefixes into variable
names instead of using the language name-space features. Otherwise you
end up with a bunch of ugly module names qpid_X, qpid_Y etc.and no way
for the programmer to say "import qpid"
The problem with that is that there is already a qpid package and a messaging
module within that. The swigged client actually depends on another module from
the qpid package, but is otherwise separately built at present.
qpidc.messaging is another option (I personally doubt whether there will be any
other modules in that package, but I have no objection to that).
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
So is it the case that we have 2 versions of the Qpid messaging interface: one
in python and one swigged?
In that case how about qpid.messaging and qpid.messagingc? Its the package
that's different, not the containing project.
Cheers,
Alan.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
