<div dir="ltr">Ben,<br><br><span style="font-family: courier new,monospace;">setup_channel(Connection, Realm) -></span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> Channel = amqp_connection:open_channel(Connection),</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> Access = #'access.request'{realm = Realm,</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> exclusive = false,</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> passive = true,</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> active = true,</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> write = true,</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> read = true},</span><br style="font-family: courier new,monospace;">
<span style="font-family: courier new,monospace;"> #'access.request_ok'{ticket = Ticket} = amqp_channel:call(Channel, Access),</span><br style="font-family: courier new,monospace;"><span style="font-family: courier new,monospace;"> {Channel, Ticket}.</span><br style="font-family: courier new,monospace;">
<br>This is used in a few places, which pass Realm around, so they will have to be changed. I also use it with the internal API to create realms using Erlang, but of course I am not complaining about that changing.<br><br>
Regards,<br>Edwin<br><br><div class="gmail_quote">On Tue, Aug 5, 2008 at 11:58 AM, Ben Hood <span dir="ltr"><<a href="mailto:0x6e6562@gmail.com">0x6e6562@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Edwin,<br>
<br>
On Tue, Aug 5, 2008 at 4:12 PM, Edwin Fine<br>
<div class="Ih2E3d"><<a href="mailto:rabbitmq-discuss_efine@usa.net">rabbitmq-discuss_efine@usa.net</a>> wrote:<br>
</div><div class="Ih2E3d">> Ben,<br>
><br>
> Um, does this mean that:<br>
><br>
> In rabbitmqctl,<br>
><br>
> add_realm <VHostPath> <RealmName><br>
> delete_realm <VHostPath> <RealmName><br>
> list_realms <VHostPath><br>
> set_permissions <UserName> <VHostPath> <RealmName> [<Permission> ...]<br>
><br>
> will disappear?<br>
<br>
</div>Yes.<br>
<div class="Ih2E3d"><br>
> Furthermore, does this mean that our code will have to remove all references<br>
> to realms? Or are you leaving all that syntax in place but just making it a<br>
> NOOP?<br>
<br>
</div>If you using an internal API, e.g. rabbitmqctl, then yes, we are<br>
removing all references to it.<br>
<br>
Internal APIs are always subject to change.<br>
<br>
If you are using the wire protocol, the access.request command and<br>
usage of tickets will become NOOPs.<br>
<br>
Also, although I can't say with any certainty, because it is pending a<br>
vote by the working group on 0-9 SP1, the fields *may* also be removed<br>
from the wire format.<br>
<br>
However, if you are using the Erlang client, this will be transparent to you.<br>
<br>
Just out of interest's sake, what functionality are you actually using<br>
wrt to realms?<br>
<br>
HTH,<br>
<font color="#888888"><br>
Ben<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>For every expert there is an equal and opposite expert - Arthur C. Clarke<br>
</div>