User Tools

Site Tools


ipacketserializationservice

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
ipacketserializationservice [2026/08/15 07:17] – divineripacketserializationservice [2026/08/15 07:23] (current) – diviner
Line 1: Line 1:
 ===== IPacketSerializationService ===== ===== IPacketSerializationService =====
  
-This service is responsible for serializing [[IEntity|Entities]] into [[EntityPacket|EntityPackets]] and applying EntityPacket data back onto existing Entities. Component state is serialized through the packet serialization strategy associated with each supported [[IComponent|Component]] type. Only Components that have a registered serialization strategy are serialized; Components without a corresponding strategy are ignored and do not contribute data to the EntityPacket.+This service is responsible for serializing [[IEntity|Entities]] into [[EntityPacket|EntityPackets]] and applying EntityPacket data back onto existing Entities. Component state is serialized through the packet serialization strategy associated with each supported [[IComponent|Component]] type. Only Components that have a registered [[IPacketSerializationStrategy|serialization strategy]] are serialized; Components without a corresponding strategy are ignored and do not contribute data to the EntityPacket.
  
 Component packets may be serialized using either encoded packet identifiers or packet type names. Encoded packets reduce serialized size by replacing type names with numeric identifiers, but depend on the packet registration ordering remaining compatible between serialization and deserialization. Non-encoded packets use packet type names and are therefore more robust when packet types are added or changed. Component packets may be serialized using either encoded packet identifiers or packet type names. Encoded packets reduce serialized size by replacing type names with numeric identifiers, but depend on the packet registration ordering remaining compatible between serialization and deserialization. Non-encoded packets use packet type names and are therefore more robust when packet types are added or changed.
ipacketserializationservice.1786778256.txt.gz · Last modified: by diviner

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki