The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
Task for WebSocket communication ?
We have Perfomance issues.
Currently setting up a communication between a Hololens and a server, we are seeking to spread it through 4 different WebSockets
Up until now, We've been using 2 tasks for every WebSocket, one to send messages and an other which reads the buffer in a loop. It works so far, nevertheless it leads to lagging issues including a mediocre frame rate.
What could you suggest would be the best way to fragment the communication between a Hololens and a server?