Attempt to reconnect at startup until a success finally happens
Fail immediately if first connection fails
This issue is to extend 1. The first option may sometimes be the desired behavior, however, the initial connect future will not resolve until at least one success happens. This may cause the StubbornIo/TCP to block an async task indefinitely, until it happens. There are use cases in which a user may want the connect Future to proceed, even though it did not successfully complete, since they know that it will continue to try to reconnect behind the scenes.
Currently I support the following:
This issue is to extend 1. The first option may sometimes be the desired behavior, however, the initial connect future will not resolve until at least one success happens. This may cause the StubbornIo/TCP to block an async task indefinitely, until it happens. There are use cases in which a user may want the connect Future to proceed, even though it did not successfully complete, since they know that it will continue to try to reconnect behind the scenes.