How Custom Decodes Are Used Within Transaction Analyzer

When writing a custom decode for a given protocol, you should understand how the decoded information is used within Transaction Analyzer. For the packet displayed in Figure 1 (an HTTP GET message), there is a separate summary decode line for each of the protocols recognized by Transaction Analyzer (in this case, DLC, IP, TCP, and HTTP). One of the responsibilities of a decoder for a given protocol is to create the summary line.

Figure 1: Example Decode

Example decode display for an HTTP GET packet

In Figure 1, you can see that the HTTP summary line has been expanded to show additional details about the HTTP protocol header for this packet. This is the other primary responsibility of a decoder: to create a series of detail lines for a protocol.