PixelStreamingInfrastructure/Matchmaker
Matthew Cotton ddc51513ca
Some small fix ups from the PR review.
2024-02-29 09:15:29 +11:00
..
Docs Shift of Matchmaker and SFU pages to Infra 2023-09-13 11:38:34 +10:00
html/sample
modules
platform_scripts Update platform scripts so that the BASH_LOCATION works on Mac as well (#428) 2023-11-16 16:19:40 +10:00
.gitignore Adding https support. 2024-02-21 17:31:00 +11:00
README.md
config.json Some small fix ups from the PR review. 2024-02-29 09:15:29 +11:00
matchmaker.js Some small fix ups from the PR review. 2024-02-29 09:15:29 +11:00
package-lock.json
package.json Have matchmaker ask for authentication instead of EACCES (#333) 2023-07-27 10:04:17 +10:00

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.

Docs