caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Anders Peter Fugmann <anders@fugmann.net>
To: Marek Kubica <marek@xivilization.net>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] ocaml-amqp 0.0.1
Date: Thu, 12 Nov 2015 23:33:11 +0100	[thread overview]
Message-ID: <564513A7.1040805@fugmann.net> (raw)
In-Reply-To: <20151112223753.0f8b7145@xivilization.net>

On 12/11/15 22:37, Marek Kubica wrote:
> Hello,
>
> On Sat, 7 Nov 2015 19:45:10 +0100
> Anders Peter Fugmann <anders@fugmann.net> wrote:
>
>> Please let me know how it works out.
>
> I tried it and it seems to be working quite well. Very nice. Sending a
> message based on the tests/main.ml works just fine, receiving it with
> pika was no problem, similarly receiving with Langohr worked just as
> well.
Glad to hear that.
Btw, which amqp-server have you tested against?

>
> My biggest problem has, in fact been Async itself. As I tried to send a
> single message via AMQP and then terminate the program I added the
> Queue.publish call and then >>='d in a function which calls Async's
> Shutdown. Unfortunately this terminates the Scheduler before it has a
> chance to send the message. Need to explore more of Async to figure out
> how to wait for the Deferred.t to be realized before shutting down.
Async is not to blame here.

The answer should have been 'just close the channel / connection to make 
sure all queues are flushed', but it seems I forgot to implement it. I 
will try and implement it this weekend, along with per message and per 
queue flushing.

In the meantime, if you are using rabbitmq then you can enable confirms 
when creating the channel. Publishing will then return only when 
rabbitmq has acknowledged the message.

>
>> Please be aware that even though I do not expect major changes to the
>> API, the library is still in heavy development. Please send feedback,
>> including suggestions on the API so that these can be incorporated
>> into the next version.
>
> So far I haven't had issues with the API. But having some searchable
> docs published somewhere would definitely be helpful.
I don't know how to make is searchable, but ocamldoc generated 
documentation is available there:

http://andersfugmann.github.io/ocaml-amqp/

>
> regards,
> Marek
>

/Anders



      reply	other threads:[~2015-11-12 22:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-01  8:05 Anders Peter Fugmann
2015-11-07 14:32 ` Marek Kubica
2015-11-07 18:45   ` Anders Peter Fugmann
2015-11-12 21:37     ` Marek Kubica
2015-11-12 22:33       ` Anders Peter Fugmann [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=564513A7.1040805@fugmann.net \
    --to=anders@fugmann.net \
    --cc=caml-list@inria.fr \
    --cc=marek@xivilization.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).