charleslemaux/Mirror
1
0
Fork 0
mirror of https://github.com/MirrorNetworking/Mirror.git synced 2024-11-18 11:00:32 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Better grammar and typos

Browse Source
This commit is contained in:
Paul Pacheco 2019-03-11 18:23:42 -05:00 committed by GitHub
parent b9c5aefcc1
commit 6eb2baaf55
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/Transports/Multiplexer.md
View File

@ -2,7 +2,7 @@
The MultiplexTransport is not a transport itself, but it allows you to combine other transports so that your clients can connect to your servers via either one of them.
A prime use case for the MultiplexTransport is having a server that listens to both websockets and TCP (or an RUDP transport). Your web based clients can connect to the server using websockets, and your mobile or desktop clients can connect to the same server via TCP or other transports and interact with each other. In HLAPI, you had to chose between websockets and UDP, but you could not use both at the same time. While the most common use case is websocket + TCP, you can configure any number of transports in the multiplex transport.
A common use case for the MultiplexTransport is a server listening to both websockets and TCP. Your webgl clients can connect to the server using websockets and your mobile or desktop clients can connect to the same server via TCP. In HLAPI, you had to chose between websockets and UDP, but you cannot use both at the same time. You can configure any number of transports in the MultiplexTransport.
To use the MultiplexTransport follow these steps:
@ -14,7 +14,7 @@ To use the MultiplexTransport follow these steps:
6. Add the TelepathyTransport component to the MultiplexTransport as the first transport
7. Add the WebsocketTransport component to the MultiplexTransport as the second transport
Please note that Telepathy and WebsocketTransport cannot listen to the same port. By default Telepathy listens to 7777 and the websocket transport listents to 7778. If you change this configuration, make sure they use different ports.
Please note that Telepathy and WebsocketTransport cannot listen to the same port. By default Telepathy listens to 7777 and the websocket transport listens to 7778.
If you build your game as a webgl game, the TelepathyTransport will be skipped and your client will use the websocket transport. If you build your game as a mobile or desktop app, it will choose TelepathyTransport. The server will happily accept connections from both.