The patch teaches packet library to truncate padding octets.
The protocol class that knows its payload length should set its payload
length as payload_length > 0 attributes.
Then, the packet.parser truncates its payload.
If payload_length = 0, do nothing.
Cc: YAMAMOTO Takashi
Cc: Shaun Crampton
When would payload_length differ from payload_length_? Seems like they
should have the same value so why not use payload_length everywhere?
-Shaun
On 02/06/2013 23:50, "YAMAMOTO Takashi" wrote:
>> The patch teaches packet library to truncate padding octets.
>> The protocol class that knows its
On Mon, Jun 03, 2013 at 03:50:41PM +0900, YAMAMOTO Takashi wrote:
> > The patch teaches packet library to truncate padding octets.
> > The protocol class that knows its payload length should set its payload
> > length as payload_length_ > 0 attributes.
> > Then, the packet.parser truncates its payl
> The patch teaches packet library to truncate padding octets.
> The protocol class that knows its payload length should set its payload
> length as payload_length_ > 0 attributes.
> Then, the packet.parser truncates its payload.
> payload_length_ is used to avoid name clash with ipv6.payload_lengt
The patch teaches packet library to truncate padding octets.
The protocol class that knows its payload length should set its payload
length as payload_length_ > 0 attributes.
Then, the packet.parser truncates its payload.
payload_length_ is used to avoid name clash with ipv6.payload_length.
Cc: Sh
