You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by trivedi_ravi13 <tr...@yahoo.co.in> on 2015/10/09 15:27:05 UTC
Bind control in Python messaging APIs
Is there a control in qpid python messaging APIs if we don't want to create
or bind the queue ( already done by some one else ) but just want to send or
receive the message ? I am using ACL and some of the applications are not
allowed to perform any action except send or receive. Like in old client
APIs we had different APIs for create and bind.
--
View this message in context: http://qpid.2158936.n2.nabble.com/Bind-control-in-Python-messaging-APIs-tp7632090.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Bind control in Python messaging APIs
Posted by Jakub Scholz <ja...@scholz.cz>.
Yes, this should work also in the C++ version of the Qpid Messaging API as
well as in the Java JMS client (the one for AMQP 0-10).
Jakub
On Fri, Oct 9, 2015 at 4:12 PM, trivedi_ravi13 <tr...@yahoo.co.in>
wrote:
> Thanks for the reply, sorry to bother you again, is it possible for the
> java
> apis as well ? we have all kind of applications developed in c++, python
> and java
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/Bind-control-in-Python-messaging-APIs-tp7632090p7632092.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
Re: Bind control in Python messaging APIs
Posted by trivedi_ravi13 <tr...@yahoo.co.in>.
Thanks for the reply, sorry to bother you again, is it possible for the java
apis as well ? we have all kind of applications developed in c++, python
and java
--
View this message in context: http://qpid.2158936.n2.nabble.com/Bind-control-in-Python-messaging-APIs-tp7632090p7632092.html
Sent from the Apache Qpid users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Bind control in Python messaging APIs
Posted by Jakub Scholz <ja...@scholz.cz>.
For receiving messages, you can try to use address like this when creating
the receiver:
<queueName>; { node: { type: queue } , create: never , mode: consume ,
assert: never }
For sending you can either use the same to publish messages directly to the
queue or if you need to send the message to some specific exchange with
some routing key, you can use this:
<exchange>/<routingKey>; { node: { type: topic }, create: never }
These addresses should not create anything. The only ACL rights they need
are the "access" right to verify that the queue / exchange exist and the
consume/publish right.
Jakub
On Fri, Oct 9, 2015 at 3:27 PM, trivedi_ravi13 <tr...@yahoo.co.in>
wrote:
> Is there a control in qpid python messaging APIs if we don't want to create
> or bind the queue ( already done by some one else ) but just want to send
> or
> receive the message ? I am using ACL and some of the applications are not
> allowed to perform any action except send or receive. Like in old client
> APIs we had different APIs for create and bind.
>
>
>
> --
> View this message in context:
> http://qpid.2158936.n2.nabble.com/Bind-control-in-Python-messaging-APIs-tp7632090.html
> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>