Wrong mailing list. Apologies. Please ignore.
On Fri, Dec 8, 2017 at 11:04 AM, Arthur Naseef wrote:
> Note that I'm doing much of this for the first time, and not finding
> examples on the website, so I expect there's a good chance I'm missing
> something.
&g
Note that I'm doing much of this for the first time, and not finding
examples on the website, so I expect there's a good chance I'm missing
something.
Summary of the problem:
* Clients get pinned to a single broker url when attempting to connect,
when using infinite connect attempts.
Backgroun
nder which
> conditions?
>
> If we add your proposal as an additional initializer implementation, we
> will also have to update the user's guide and give our users appropriate
> recommendations when they should use which class.
>
> And, we will have to pick a meaningful name for your
A few questions coming to mind here:
- First off, how do we move this forward?
- What do we do with the new implementation?
- What is a good way to address the busy-wait in the original code?
- What is a good way to address the fact that all threads will
busy-wait in the
