hm, i am not sure. Because connection pooling is more than one connection. I need just one but keep it always available (reconnect on errors). On July 17, 2014 at 6:01:38 PM, Phillip Simbwa ([email protected]) wrote:
Are you looking for the equivalent of connection pooling on the client side? On Fri, Jul 18, 2014 at 2:01 AM, Denis Samoilov <[email protected]> wrote: > hi community, > > currently i use per call connection but due increase of communication > thinking to move to the model with always open connection. In this case I > need to handle situation when connection is lost and reopen it. > > What is right way to do this? Do I need to recreate client after connection > lost? Because simply transport->open() does not work. Also, what would be > correct exception to catch (currently i think to reconnect on any > exception)? > > Thank you! > -- - Phillip. "Aoccdrnig to rscheearch at an Elingsh uinervtisy, it deosn't mttaer in waht oredr the ltteers in a wrod are, the olny iprmoetnt tihng is taht the frist and lsat ltteer are in the rghit pclae. The rset can be a toatl mses and you can sitll raed it wouthit a porbelm. Tihs is bcuseae we do not raed ervey lteter by it slef but the wrod as a wlohe and the biran fguiers it out aynawy."
