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

SteamClient should be able to use TCP and UDP connections when both ProtocolTypes are specified #417

Closed
yaakov-h opened this issue Jul 22, 2017 · 0 comments
Assignees
Milestone

Comments

@yaakov-h
Copy link
Member

Currently if a server supports both TCP and UDP and both ProtocolTypes are permitted, SteamClient will only use TCP.

We should enhance SteamClient / SmartCMServerList to treat TCP and UDP for the same address as two different servers, but load and serialise them as one.

@yaakov-h yaakov-h added this to the 2.0.0 milestone Jul 22, 2017
@yaakov-h yaakov-h self-assigned this Jul 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant