Skip to content
This repository has been archived by the owner on May 3, 2022. It is now read-only.

Using host names as well as IPv4 addresses #327

Open
yhorbachov opened this issue Jun 9, 2016 · 3 comments
Open

Using host names as well as IPv4 addresses #327

yhorbachov opened this issue Jun 9, 2016 · 3 comments

Comments

@yhorbachov
Copy link

Right now tchannel accepts only IPv4 addresses to create socket. tchannel uses standard node 'net' module which accepts host names and IPv4 addresses. I believe we should allow users use any format which they want.

@Raynos
Copy link
Contributor

Raynos commented Aug 16, 2016

That doesn't actually work due to cross-language compatibility and init headers.

An IP is expected, we could resolve the hostname for you... but you might as well just give us an IP.

However, tcurl should support this.

@prashantv
Copy link
Contributor

Yep, I filed an issue on tcurl a while ago,
uber-node/tcurl#125

Agree that it should be done outside of tchannel-node.

nathanboktae pushed a commit to cadence-workflow/cadence-web that referenced this issue Jan 23, 2018
@Choongkyu
Copy link

related to this, how would we allow for 0.0.0.0? it looks like this can be enabled if allowEmphemeral(sic) is true, but I'm not seeing a way to set this to be true from the user. I'm having trouble with connections being refused when trying to call across pods using the cluster ip. Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants