charleslemaux/Mirror
1
0
Fork 0
mirror of https://github.com/MirrorNetworking/Mirror.git synced 2024-11-18 19:10:32 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
e9286b8259
Mirror/doc/Articles/Transports/Telepathy.md
James Frowen b86a611674
Restructure docs (#2249) 
* moving all guides to Articles folder

* updating toc for root and articles

* fixing toc

* css on side toc

* fixing links on index
2020-09-16 22:27:05 +01:00

1.7 KiB
Raw Blame History

Telepathy Transport

Simple, message based, MMO Scale TCP networking in C#. And no magic.

  • Telepathy was designed with the KISS Principle in mind.
  • Telepathy is fast and extremely reliable, designed for MMO scale Networking.
  • Telepathy uses framing, so anything sent will be received the same way.
  • Telepathy is raw C# and can be used in Unity3D too.
  • Telepathy is available on GitHub

What makes Telepathy special?

Telepathy was originally designed for uMMORPG after 3 years in UDP hell.

We needed a library that is:

  • Stable & Bug free: Telepathy uses only 400 lines of code. There is no magic.
  • High performance: Telepathy can handle thousands of connections and packages.
  • Concurrent: Telepathy uses one thread per connection. It can make heavy use of multi core processors.
  • Simple: Telepathy takes care of everything. All you need to do is call Connect/GetNextMessage/Disconnect.
  • Message based: if we send 10 and then 2 bytes, then the other end receives 10 and then 2 bytes, never 12 at once.

MMORPGs are insanely difficult to make and we created Telepathy so that we would never have to worry about low level Networking again.

What about...

  • Async Sockets: didn't perform better in our benchmarks.
  • ConcurrentQueue: .NET 3.5 compatibility is important for Unity. Wasn't faster than our SafeQueue anyway.
  • UDP vs. TCP: Minecraft and World of Warcraft are two of the biggest multiplayer games of all time and they both use TCP networking. There is a reason for that.