Improving net's deadline support

[Gustavo Niemeyer]

Right now we can only have a timeout during the dial or name
resolution phase if we use the net.Dial function, but not with any of
the other Dial* and Resolve* functions.

Is there anyone working ATM to improve this situation, or do we at
least have a plan on how to do so? Looking at net.Dialer, perhaps the
plan was to have other methods available there, but we never had the
time to do it?


gustavo @ http://niemeyer.net

[Brad Fitzpatrick]

net.Dialer is a superset of all the Dial* funcs.

So what do you actually want? To Resolve* with a timeout efficiently?

I would be fine with a net.Dialer.Resolve method, but it's passed the deadline.  File an issue?

--

---
You received this message because you are subscribed to the Google Groups "golang-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Brad Fitzpatrick]

s/passed/past/  Nice.

[Gustavo Niemeyer]

On Tue, Sep 3, 2013 at 12:35 PM, Brad Fitzpatrick <brad...@golang.org> wrote:
> net.Dialer is a superset of all the Dial* funcs.

That's not quite true. If one has a net.TCPAddr, there's no way to
dial it other than stringifying and submitting it to the
parser/resolver again.

> So what do you actually want? To Resolve* with a timeout efficiently?

Right, and DialTCP.

> I would be fine with a net.Dialer.Resolve method, but it's passed the
> deadline. File an issue?

Will do, thanks.


gustavo @ http://niemeyer.net

[Brad Fitzpatrick]

A stringified TCPAddr won't re-resolve though.

But if it really matters, we could have a DialAddr method on Dialer.

[Gustavo Niemeyer]

Issue filed: http://golang.org/issue/6340

--

gustavo @ http://niemeyer.net