Re: The un-reactor

2015-10-22 Thread Cliff Jansen
I'm not sure if this exactly fits your question (especially the multi-threaded part), but the python tornado loop examples run a regular reactor set of events and collectors but driven by the external loop. pn_iohandler is replaced with the TornadoLoophandler which knows how to insert Proton io se

The Go electron API: a tale of two brokers.

2015-10-22 Thread aconway
The Go binding for proton provides 2 alternate APIs, `proton` is an exact analogue of the event-driven proton C API and `electron` which is a more go-oriented, procedural API. The differences were motivated by the concurrency features of the Go language but there may be lessons to learn for other l

The un-reactor

2015-10-22 Thread aconway
The proton reactor provides a complete solution for integrating foreign IO into a single threaded proton event loop. This is useful in situations where proton is being used in isolation, there is no other IO handling framework available and everything is single threaded. However often that is not

Re: Error recovery in qpidd / proton communication

2015-10-22 Thread Michael Ivanov
Thanks for the advice, I am using messenger in passive mode integrating it into select-driven event loop. Mayxbe reactor would be more appropriate, but I have checked the proton api documentation and al reactor functions are regrettably uncommented. Where can I find c++ examples? Best regards,

Re: Error recovery in qpidd / proton communication

2015-10-22 Thread aconway
On Thu, 2015-10-22 at 18:20 +0300, Michael Ivanov wrote: > Hallo, > > What kind of communication error recovery is available in proton > library (if at all)? > I am using proton messenger in passive mode and I noticed very > unpleasant behaviour: > wherever the connection to qpidd is broken (eg. w

Error recovery in qpidd / proton communication

2015-10-22 Thread Michael Ivanov
Hallo, What kind of communication error recovery is available in proton library (if at all)? I am using proton messenger in passive mode and I noticed very unpleasant behaviour: wherever the connection to qpidd is broken (eg. when qpidd is restarted), the client progan does not seem to get any

Re: Difference between Apache Qpid and Redhat MRGM broker

2015-10-22 Thread Gordon Sim
On 10/22/2015 05:37 AM, rishibhargava wrote: Not sure if this is already discussed here, we are currently using Redhat MRGM in one of our application and want to migrate to Apache Qpid. The Red Hat rpm containing qpidd are built from 'pristine' source of a given qpid public release (indicated

Difference between Apache Qpid and Redhat MRGM broker

2015-10-22 Thread rishibhargava
Hi Guys, Not sure if this is already discussed here, we are currently using Redhat MRGM in one of our application and want to migrate to Apache Qpid. -- View this message in context: http://qpid.2158936.n2.nabble.com/Difference-between-Apache-Qpid-and-Redhat-MRGM-broker-tp7632627.html Sent fr