Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

remove client passive move #27

Open
kofemann opened this issue Jan 26, 2023 · 1 comment
Open

remove client passive move #27

kofemann opened this issue Jan 26, 2023 · 1 comment

Comments

@kofemann
Copy link
Member

The original dcap implementation was based on a model where dcache pool connect to the client for the data path. Now days so called passive mode is preferred, where client initializes both control and data connections, as this is more firewall friendly behavior. The old functionality is mostly not used and/or source of unexpected problems, thus should be removed.

@kofemann
Copy link
Member Author

@ellert I suggest we drop old behavior and bump client version to 2.48.0

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

No branches or pull requests

1 participant