Bas Wegh

Crossbar handles it by using the : REGISTER.Options.invoke = first | last | roundrobin | random | single (default) see: http://crossbar.io/docs/Shared-Registrations/

what is the difference between "hot standby" and REGISTER.Options.invoke = first ?

I understand your use case, what I do is just return an "ok" to the caller and let everyone process the events, including the caller. This way I know that...

It should be in the documentation of both, bw-listing and event history stated that bw-listing based on IDs MUST NOT be stored in the event-history. In contrast to bw-listing on...

yes, exactly that is the issue, @goeddea

hi Robert, I moved to cargotube, which is a reimplementation of erwa using new Erlang features and trying to avoid the mistakes made in erwa. https://github.com/CargoTube/cargotube can you please give...

could you please describe what you are doing? so I can see where the issue is coming from, thanks

using meck, check documentation at https://github.com/eproxus/meck

a pity this has not been included before upgrading to 0.18

please have a look again and eventually accept this PR, thanks in advance