Skip to content

feat: Add support for connecting via a hostname instead of IP [MTT-10139] #3440

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

Merged
merged 13 commits into from
May 16, 2025

Conversation

ShadauxCat
Copy link
Collaborator

@ShadauxCat ShadauxCat commented May 6, 2025

Add support for connecting via a hostname instead of IP when using supported versions of unity and unity transport.

Changelog

  • Added: When using UnityTransport >=2.4 and Unity >= 6000.1.0a1, SetConnectionData will accept a fully qualified hostname instead of an IP as a connect address on the client side.

Testing and Documentation

  • No tests have been added. (Manual tests were performed. The CI environment doesn't have "localhost" consistently defined to be able to run automated tests.)
  • Includes edits to existing public API documentation.

Backport

Backport of #3441

…pported versions of unity and unity transport.
@ShadauxCat ShadauxCat requested review from NoelStephensUnity, EmandM and a team as code owners May 6, 2025 16:54
@ShadauxCat ShadauxCat changed the title Add support for connecting via a hostname instead of IP [MTT-10139] feat: Add support for connecting via a hostname instead of IP [MTT-10139] May 6, 2025
ShadauxCat and others added 7 commits May 6, 2025 16:32
Bringing  the updates from #3441 to the v1.x.x branch.
Increasing disconnect timeout period to account for a system running slower than expected.
Re-arranging parameters and permission level of the two InitializeTransport methods.
Changing some new public things to internal things.
one more PVP public issue... >.< (p....v.....p)
removing whitespaces
Adjustments made to ConnectionAddressData and adjustments to tests.
NoelStephensUnity added a commit that referenced this pull request May 15, 2025
Add support for connecting via a hostname instead of IP when using
supported versions of unity and unity transport.

## Changelog

- Added: When using UnityTransport >=2.4 and Unity >= 6000.1.0a1,
`SetConnectionData` will accept a fully qualified hostname instead of an
IP as a connect address on the client side.

## Testing and Documentation

- No tests have been added. (Manual tests were performed. The CI
environment doesn't have "localhost" consistently defined to be able to
run automated tests.)
- Includes edits to existing public API documentation.

## Backport

Backport:
#3440

---------

Co-authored-by: NoelStephensUnity <noel.stephens@unity3d.com>
@NoelStephensUnity NoelStephensUnity enabled auto-merge (squash) May 15, 2025 16:56
@NoelStephensUnity NoelStephensUnity merged commit a212f36 into develop May 16, 2025
40 checks passed
@NoelStephensUnity NoelStephensUnity deleted the feat/connect_using_hostname branch May 16, 2025 01:37
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.

4 participants