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.
What exactly are Sharing Service Client Roles?
Okay, so I've been abstracting the Sharing code from Holograms 240 for our needs, and understand most of what I am seeing here, but I am a little stumped on what the Client Roles are.
Instinct tells me that a Primary Client starts and terminates the service, whilst a Secondary Client can only join and leave and existing service? However, through testing across two devices, I am unsure if this is the case. So, what exactly are the differences between the two roles?
If my instinct serves me wrong, does the existing codebase have a way of having one user responsible for starting and terminating the service, whilst others can only join and leave?
When both devices quit the application whilst testing, the Sharing Service does not currently terminate, is there a command I can send it? Or do I simply call session.Dispose()? When both devices restarted the application during our testing, we found that the spatial mapping and anchors had gone wrong, and my coworkers avatar was to my left, whilst he was standing in front of me.
I apologise for the numerous questions, but if I can nail down these concepts, I can build what we need.