On Fri, Sep 7, 2012 at 4:10 AM, <[email protected]> wrote: > tcp.data already exists for exposing a single TCP segment's payload as a byte > array. It would be handy to have something similar for a single application > layer PDU when TCP segment reassembly is involved. I propose > tcp.reassembled.data, named and placed after the already existing field > tcp.reassembled.length.
What is the functional difference between tcp.segments and tcp.reassembled.data? They both provide the reassembled data, and I think this looks like a duplicate field. Or do I miss something here? The reason I ask is because I was thinking about this when implementing reassembled.length, but found the existing field (hf_fragments) sufficient for all practical use. And yes, I know this question is a bit late :) -- Stig Bjørlykke ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
