[rabbitmq-discuss] RabbitMQ logs, ticket check

Edwin Fine rabbitmq-discuss_efine at usa.net
Tue Aug 5 20:28:05 BST 2008

Matthias, thanks for the very clear answer.

I don't have any attachment to or need for realms, so as far as I am
concerned, they can disappear and won't be missed. I will definitely remove
realm-related items from my code once they become NOOPs.


On Tue, Aug 5, 2008 at 1:20 PM, Matthias Radestock <matthias at lshift.net>wrote:

> Edwin,
> Edwin Fine wrote:
>> setup_channel(Connection, Realm) ->
>>    Channel = amqp_connection:open_channel(Connection),
>>    Access = #'access.request'{realm = Realm,
>>                               exclusive = false,
>>                               passive = true,
>>                               active = true,
>>                               write = true,
>>                               read = true},
>>    #'access.request_ok'{ticket = Ticket} = amqp_channel:call(Channel,
>> Access),
>>    {Channel, Ticket}.
>> This is used in a few places, which pass Realm around, so they will have
>> to be changed.
> The above will continue to work until realms & tickets are removed from the
> protocol.
> We are going to be removing realms & tickets in the following stages:
> 1) Removal from the server internals and admin interface. Application code
> using the APIs of the various clients, and code that uses the AMQ protocol
> directly, will largely be unaffected since the protocol methods haven't
> changed and the server continues to respond to access.request method. Only
> code that that actively relies on the access control provided by realms will
> break with this change. I don't think there is much of that about.
> 2) Removal from the high-level client APIs. This will require some changes
> to application code, but these should all be very straightforward. Also note
> that there is nothing forcing you to upgrade to the new versions of the
> client; the old clients will continue to function. And code that uses the
> AMQP protocol more directly, such as the code above, will remain unaffected.
> 3) Removal from the protocol. At this point all application code must use
> the new client APIs and code that uses the AMQP protocol more directly will
> need to be changed. Again, the changes should be straightforward.
> We are about to carry out step 1. Step 2 is still a few weeks off. And step
> 3 won't happen until after the AMQP Working Group has published a spec which
> removes realms & tickets.
> Hope the above is ok with everybody; if, otoh, you are really fond of
> tickets and realms and don't want to live without them then please let us
> know :)
> Matthias.

For every expert there is an equal and opposite expert - Arthur C. Clarke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20080805/b9919b79/attachment.htm 

More information about the rabbitmq-discuss mailing list