[rabbitmq-discuss] Erlang client now works on default and has some(important) API changes

Chris Chew chrisch at ecollege.com
Mon Sep 13 16:06:09 BST 2010

Hello Everyone.

Thank you for the update, Vlad.

Just to confirm...is it still recommended for an erlang client that
works against broker 2.0.0 to update the public umbrella to the
rabbitmq_v2_0_0 tag and build from there?


Chris Chew

-----Original Message-----
From: rabbitmq-discuss-bounces at lists.rabbitmq.com
[mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Vlad
Alexandru Ionescu
Sent: Monday, September 13, 2010 7:31 AM
To: RabbitMQ
Subject: [rabbitmq-discuss] Erlang client now works on default and has
some(important) API changes

The Erlang client was broken on default recently. We have now fixed it 
and it works with the latest version of the broker on default.
We recommend people that were using branches bug22993 or bug23024 to use

the version on default instead (if you were using the latest broker 
version and not 2.0.0).

Please note that there have been some API changes as well:

functions have been replaced by amqp_connection:start/{1,2}. Example

     amqp_connection:start(network, #amqp_params{heartbeat = 20}).

- amqp_connection:start/{0,1} functions do not return ConnectionPid. 
They return {ok, ConnectionPid} or {error, Error} instead:

     {ok, ConnectionPid} = amqp_connection:start(network).

- amqp_connection:open_channel/1 does not return ChannelPid. It returns 
{ok, ChannelPid} or {error, Error} instead:

     {ok, ChannelPid} = amqp_connection:open_channel(ConnectionPid).

The edoc is to be updated soon.
We hope that this will be the final version of the API, but cannot 
guarantee this until the Erlang client will become officially supported.


rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com

More information about the rabbitmq-discuss mailing list