class design on network packet parsing

Question

I am looking for suggestions or design patterns to handle the parsing and generation of network packets (network or not by itself is not important per se). Each packet has a fixed length header and a variable length payload. The payload parsing will depend on the packet type. The straightforward way of doing this would be (assuming the input will come from a stream, console or network):

class Header {
public:
   Header(istream &);
   istream& read(istream &);
private:
   uint32_t type;
   uint32_t payload_length;
}

class PayloadTypeA {
public:
   PayloadTypeA {}
   istream& read(istream &);
private:
   uint32_t payload_1;
   uint32_t payload_2;
}

class PayloadTypeB {
 ...
}

The way I envision for the processing logic would be: read header first, then check the packet type, then decide which payload type to use to read the rest.

However, I feel this solution seems somewhat clumsy - I wonder if there is a better solution or design idioms I should follow?

thanks

Oliver

Adrian · Accepted Answer · 2012-02-07 19:35:04Z

1

Usually, your header is something like this:

Contents in brackets [ ] is header data

[Header length, Data Type,] Data

If you want, you can have a dynamic header (of variable length):

[Header Length, Number of Chunks, Size of chunk 1, Size of chunk 2, Size of chunk 3 etc, Data Type,] Data

You can create your own custom header to match whatever you're sending.

answered Feb 7, 2012 at 19:35

Adrian

5,6808 gold badges57 silver badges90 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

class design on network packet parsing

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest