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

Websocketpp unique port in case of Citirx Xenapp environment #747

Open
HimanshuNandu opened this issue Aug 14, 2018 · 2 comments
Open

Websocketpp unique port in case of Citirx Xenapp environment #747

HimanshuNandu opened this issue Aug 14, 2018 · 2 comments

Comments

@HimanshuNandu
Copy link

I have a JavaScript websocket client app and c++ desktop websockert server app.

Requirement is to not hardcode port number and generate it at run time, Since in Citirx XenApp environment we cannot share port across user sessions as we have one c++ desktop server running for each client.

The problem is Citirix Env shared across user sessions has only one IP, so I need unique port for each user.

Since javascript has limitations reading config files, etc I cannot give back the port number to it.

Now if we hardcode the port numbers, we cannot work with Citrix, but in Citrix we can define something as virtual IP for each user session, and configure it only if the app uses windows socket APIs

Please read Citirix virtual ip doc

https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-6/xad-deliver-virtual-ip.html?_ga=2.238668864.1703096070.1534187166-889472187.1533567733

I wanted to know if internally websocketpp calls windows socket calls?

@ultimate-tester
Copy link

To answer your question, yes this library indirectly uses Windows Sockets.
All network calls will end up in some way at the Windows Sockets library.

@HimanshuNandu
Copy link
Author

Thank You...

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

2 participants