<div dir="ltr">Ben,<br><br>Thanks, I pulled down the latest client code from Mercurial, and it has lib_amqp in it. I'll look at pulling down the server code, but please understand that I actually need this stuff working by tomorrow, so I may have to kluge something in the meantime, which I promise never to give to you ;) But at least it will give me some experience so I mostly know what to expect in the new code base.<br>
<br>Regards,<br>Ed<br><br><div class="gmail_quote">On Sun, Sep 7, 2008 at 9:01 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 Sun, Sep 7, 2008 at 8:48 AM, 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">> needed to get things up and running). I am going to make my own<br>
> rabbit_common OTP application, and change the Erlang client to depend on it<br>
> rather than the server. I will also see what it takes to change the rabbit<br>
> 1.4.0 server itself to factor out the common code and to use this<br>
> rabbit_common application.<br>
<br>
</div>Just FYI, please be aware that the server code base has moved on<br>
structurally since the 1.4.0 release, so you may want to code against<br>
something more recent, without of course coding against a moving<br>
target. Also, there are improvements in a branches in the client that<br>
will go back into the default branch, e.g. introduction of lib_amqp as<br>
a high level API.<br>
<font color="#888888"><br>
Ben<br>
<br>
</font></blockquote></div><br></div>