Skip to content

Conversation

@msabansal
Copy link
Contributor

For the next version of windows we have added support for network namespaces. With this support there is no need to manipulate endpoints individually. This brings windows in parity with other implementations(for networking).

Signed-off-by: Sandeep Bansal sabansal@microsoft.com

Signed-off-by: Sandeep Bansal <sabansal@microsoft.com>
@crosbymichael
Copy link
Member

I would opt for namespace since this is already in the Network structure but I can see that thing is pretty inconsistent

@lowenna
Copy link
Contributor

lowenna commented Aug 27, 2018

@crosbymichael There's a lot of inconsistency throughout where namespace is used. However, I think what Sandeep has done here is consistent with the Windows part of the spec. Hence LGTM

@dineshgovindasamy
Copy link
Contributor

Ping @crosbymichael Could you please approve this PR?

@dineshgovindasamy
Copy link
Contributor

cc @jhowardmsft

@crosbymichael
Copy link
Member

Don't you have to update the go structs as well?

@dineshgovindasamy
Copy link
Contributor

@crosbymichael i have created a new PR with the changes to go structs as well. #989

Could you please approve this PR? i will ask Sandeep to abandon this PR.

@vbatts
Copy link
Member

vbatts commented Dec 17, 2019

LGTM

Approved with PullApprove

@h-vetinari h-vetinari mentioned this pull request Feb 3, 2020
@h-vetinari
Copy link
Contributor

I didn't realise when I made the list, but this PR has been fully obsoleted by #989 and can be closed. @vbatts

@vbatts vbatts closed this Mar 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants