Client wait for connection

[jeffque]

The default behavior is (and should continue to be) for the client to fail immediately when there is no server in the port.

It would be good that, given a CLI flag, it would wait until a server is available in such port. It should retry at a regular interval to connect.

[reinaldorauch]

Hello! Something like teecp --wait ? Or --wait-connection?

[jeffque]

Hello! Something like teecp --wait ?

--wait-connection seems great! Better than my previous idea

[jeffque]

@reinaldorauch , do you think it will be intuitive to have something like --wait-connection=250 ? Meaning that it will wait for 250ms before trying again?

I am not sure if this will be a great CLI experience

[reinaldorauch]

I was about to ask if would make sense defining the timeout. I totally would use that! Also it raises the need for a interval switch I guess, like --retry-interval

Also, I think it wouldn't be difficult to parse the time unit there so the use could set --wait-connection=1s or --wait-connection=250ms like you said

[jeffque]

Agreed.

[reinaldorauch]

Nice! Just to summarize the design and the requirements:

• new option --wait-connection that makes the client wait for the connection on the port with a regular interval
• with no value specified, it waits for a default (?) time
• the user can specify a value which may or not have the time unit, which will defaults to ? (Milliseconds? Seconds?)
• the User can fully specify the value with the value and the time unit. Will check the go libs that is most common to handle these so we can leverage the pattern
• it can be used with a future new option --retry-interval that will set that value

[reinaldorauch]

Hey, opened a PR with the implementation!

[jeffque]

Solved by #9

[jeffque]

Thanks @reinaldorauch ❤️