Two ways several people can use one Eagle 3D Streaming application: each in their own session, or all watching the same one. They cost differently, and they are for different situations.
| Dedicated | Shared | |
|---|---|---|
| What each person gets | Their own session | The host's view |
| GPU machines used | One per person | One in total |
| Who can control it | Everyone, their own | The host, and whoever they hand it to |
| What they see | Independent | Identical |
| Concurrent users consumed | One each | One in total |
Everyone opens the same URL and each gets an independent session on its own machine — their own view, their own input, their own progress through the app. Nobody affects anybody else.
This is the default, and it is what you want when people are using the app rather than being shown it: a configurator where each customer builds their own product, a training scenario each person works through at their own pace.
Built on the meeting system. In the Control Panel, the application's Meeting Link tab has a Create New Meeting Link button; each meeting link has a Host Link and a Guest Link. The host starts the session with the Host Link and shares the Guest Link; everyone who joins sees the host's view of the same running application.
Guests watch by default. They cannot drive the app unless the host explicitly hands them control during the meeting, with the allow icon next to that guest's name in the participant list — which is what makes this safe for a presentation: nobody can move the camera while you are mid-sentence. Hand control to one guest at a time: two people driving at once fight over the same camera (details).
This suits a demo to a room, a design review where one person drives, or a lesson. Everyone sees the same thing at the same moment, because it is literally the same session.
Ask whether people need to do different things. If yes, dedicated. If they are all looking at the same thing while one person drives, shared — one machine instead of twenty, and everyone genuinely in step.
How concurrent users are counted, and where sessions are served from.
Last updated