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

Add protocol and API for determining metaverse that the domain server is using #247

Open
ctrlaltdavid opened this issue Jan 20, 2023 · 0 comments
Labels
enhancement New feature or request high priority

Comments

@ctrlaltdavid
Copy link
Collaborator

ctrlaltdavid commented Jan 20, 2023

If the user (app + SDK) logs into one metaverse but the domain server is using a different metaverse then things won't work.

Perhaps add a packet or pair of packets.
Perhaps add in DomainSettingsRequest and DomainSettings packet pair - esp. if metaverse server is specified in domain server settings.

Can't add the metaverse URL to just the DomainList packet because this may not be sent if the user isn't authenticated on the domain.

@ctrlaltdavid ctrlaltdavid added enhancement New feature or request high priority labels Jan 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request high priority
Projects
None yet
Development

No branches or pull requests

1 participant