Closed alexdrenea closed 7 years ago
Personally I was just talking about doing something like this recently. I worry about the system auto selecting what to connect to, but getting a list would be a great feature I think!
Totally agree that this is a great idea. Also agree that auto selection will not be ideal :)
I think having a UI/option to choose is ideal, but not critical. A lot of users (myself included) would just need an easy way to run a shared experience without worrying about changing the server IP every time. And most will only have one server running in the network so just picking the first will just work.
This PR simply exposes the DiscoveryClient classes to the SharingClient.dll so that it can be used from HoloToolkit-Unity. I can open a new issue there to figure out the best options to expose it to the end-users.
@alexdrenea I think we can leave exposing the list to end users to the application developers and that providing the developers the list is the perfect fit for the HoloToolkit!
That sounds good to me!
Hey guys, any chance to get this merged. Let me know if you think there's anything missing so I can correct it. I want to go ahead and update some of the HoloToolkit-Unity code and it would be nice to use the real HoloToolkit rather than my forks :smile:
This is merged in now.
I've noticed that Profiler Tool has a very nice feature to auto discover the server (and other clients) on the current network. I think that this would be a great feature to have on the SharingClient side so it can be integrated in your HoloLens client app. I've already made the updates and would like to see what you guys think - I'll submit the PR soon.
The idea is, that if you guys approve, we can update the HoloToolkit-Unity SharingStage class with an AutoDiscover flag that can be used instead of IP. I already have a working version of that too, but I will hold off that PR until you guys confirm that it's a good idea.