Skip to content
This repository was archived by the owner on Feb 28, 2024. It is now read-only.
This repository was archived by the owner on Feb 28, 2024. It is now read-only.

Review abstraction of packet serialization / deserialization #97

@BlowaXD

Description

@BlowaXD

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...)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions