Страница:
Handshake
Страницы
Attribute Message System
Binary Serialization
BitWriter & BitReader
Connection Approval
Core Components
Custom Transports
Dedicated Servers
Differences from UNET HLAPI
Getting Started
HLAPI Differences
Handshake
Home
Lag Compensation
Library Initialization
Limitations
Message Encryption
Message System
Modularity
NetworkConfig
NetworkProfiler Editor Window
Networked Object Pooling
NetworkedAnimator
NetworkedBehaviour
NetworkedNavMeshAgent
NetworkedObject
NetworkedTransform
NetworkedVar
NetworkingManager
Object & Behaviour Relation
Object Ownership
Object Spawning
Observer
Optimization
Passthrough Messages
Prototype Components
Roadmap
Scene Management
SyncedVars
Targeted Messages
TrackedObject
2
Handshake
Albin Corén редактировал(а) эту страницу 2018-10-16 14:10:45 +02:00
During every connection, the MLAPI does a handshake. The handshake serves a few different purposes.
- It allows for connection approval
- It allows for versioning. I.E prevent different versions from talking to each ither
- Encryption keys are created with a diffie hellman key exchange
- NetworkConfig's are checked to be the same
If the handshake doesn't complete within the Timeout time specified in the NetworkConfig, the connection will be closed. The handshake is 2 or 4 messages long depending on if Encryption is enabled.
Getting Started
The Basics
- Message System
- Object Spawning
- Object & Behaviour Relation
- Modularity
- NetworkedVar
- Scene Management
- Object Ownership
Components
Advanced Topics
- Encryption
- Networked Object Pooling
- Lag Compensation
- BitWriter & BitReader
- Custom Transports
- Optimization
- Network Profiler Window
- Dedicated Servers