Skip to content
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.

feature request: dtab updates affect persistent connections #39

Open
jasonjckn opened this issue Apr 19, 2017 · 2 comments
Open

feature request: dtab updates affect persistent connections #39

jasonjckn opened this issue Apr 19, 2017 · 2 comments

Comments

@jasonjckn
Copy link

jasonjckn commented Apr 19, 2017

currently TCP connections need to be reestablished in order to be affected #by new dtab rules, for our use case we require all connections to be 'migrated' according to new rules

@olix0r
Copy link
Member

olix0r commented Apr 19, 2017

Thanks for the suggestion @jasonjckn. Do you have any thoughts on how you would expect this to be implemented? I think the best we can do is to just tear down open connections... It doesn't really make sense to "migrate" a TCP stream, as we have no context about the state of the application running on top of it.

@jasonjckn
Copy link
Author

@olix0r yah that works for me, just closing the connections, you're right there's no good way to 'migrate' .

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

2 participants