Skip to content

ProcessMessages() #13

@austinjoseph

Description

@austinjoseph

This method barely works. There is very little hardening against false messages and the message buffer is handled very poorly.

  • It must have all of it's methods broken into smaller methods that are called for readability.
  • It must have a more robust way of verifying messages and discarding bad messages.
  • It must be able to read around the ring (currently if a message is recieved near the end of the buffer it would just be cut off
    the message procesesor should know that and reset the pointer to the beginning of the buffer to finish validating).
  • It must have a checksum implemented
  • It should liklely have a type indicator in addition to the size indicator it has now
  • It should likely be encoded in HEX string commands instead of ASCII

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions