axa 3.0.1
Farsight Security Advanced Exchange Access (AXA)
Data Structures
Here are the data structures with brief descriptions:
[detail level 12]
 C_PKAXA protocol header
 C_PKTimestamp when the NMSG message was reported
 Caxa_p_opt_uOption union
 Caxa_alias
 Caxa_ch_mask_tAXA channel mask
 Caxa_client_config_t
 Caxa_client_tAXA client state
 Caxa_emsg_tAXA error message datatype
 Caxa_helper_cache_tAXA helper cache
 Caxa_ioAXA I/O context
 Caxa_kickfile
 Caxa_nmsg_fieldAn NMSG message understood by AXA
 Caxa_nmsg_help_tAuxiliary value such as DNS class or rtype
 Caxa_nmsg_sfSome fields of some NMSG messages have a type/value structure such as JSON tags
 Caxa_p_body_tAXA protocol body
 Caxa_p_ch_buf_tNull terminated ASCII string naming an SIE channel in configuration files, sratool commands, and sratunnel args
 Caxa_p_watch_pat_tAXA protocol watch pattern
 Caxa_p_whit_tGeneric AXA protocol watch hit
 Caxa_socku_tAXA socket union
 Caxa_strbufString buffer
 Caxa_walk_opsList of DNS callback Functions
 ChitA single value for a key found in the trie and hints about the source of the data that matched the key
 Chitlist_tThe successful result of looking up a key is an array of "hits"
 Ctrie_key_tA trie key
 Ctrie_nodeThe shape of a trie node does not matter except to the trie code and to trie users that manage lists of obsolete nodes for lock-free searching
 Ctrie_roots_tThis is the handle on an AXA trie
 Ctval_listArray of values for a trie node