5bea564755
|
||
|---|---|---|
| .. | ||
| Docs | ||
| html/sample | ||
| modules | ||
| platform_scripts | ||
| .gitignore | ||
| README.md | ||
| config.json | ||
| matchmaker.js | ||
| package-lock.json | ||
| package.json | ||
README.md
Pixel Streaming Matchmaker
Instead of having all users connect to the same stream, you may want each person to end up in their own interactive experiences. To do this, you can run a separate stack of Pixel Streaming components for each user, and direct each user to a separate Signaling and Web Server to start a connection.
You can set up each stack of Pixel Streaming components on a separate host, or you can put more than one stack on the same host as long as you configure the port settings for the components within each stack so that they all communicate over different ports. See the Pixel Streaming Reference for details on these port settings.
To help set up this kind of configuration, the Pixel Streaming system can use a matchmaker server that tracks which Signaling and Web Servers are available, and whether they are being used by a client connection.