ChickenAPI
ChickenAPI copied to clipboard
Review abstraction of packet serialization / deserialization
Packet Review
Description
Actually, SaltyEmu implements a PacketSerialization class which includes everything and is mainly based on reflection, which is really slow.
I'd like to add possibilities for developers to implement both ways to use that :
- IPacketSerializer
- IPacketDeserializer
Those two interfaces should be used as "individual methods" for each packet
(1 packet = 1 serializer & 1 deserializer)
This will permit :
- OpenNos interoperability (as long as someone implement it on its source)
- NosCore interoperability (as long as NosCore is willing to implement the same packets and participate to ChickenAPI)
- SaltyEmu interoperability
Since this issue is only related to packets, it should not be hard to ask for participation from other projects (NosCore, SaltyEmu, OpenNos forks devs...)