Helium
Data Structures
Here are the data structures with brief descriptions:
 Che_clientData structure to hold all the state needed as a Helium client
 Che_conn
 Che_deprecated_msg_13
 Che_fragment_entry
 Che_fragment_entry_node
 Che_fragment_table
 Che_internal_pmtud_
 Che_internal_write_buf_
 Che_msg_auth
 Che_msg_auth_buf
 Che_msg_auth_hdr
 Che_msg_auth_response
 Che_msg_auth_token
 Che_msg_config_ipv4
 Che_msg_data
 Che_msg_data_frag
 Che_msg_extension
 Che_msg_goodbye
 Che_msg_hdr
 Che_msg_ping
 Che_msg_pong
 Che_msg_server_config
 Che_msg_session_request
 Che_msg_session_response
 Che_network_config_ipv4
 Che_packet_buffer
 Che_plugin_chain
 Che_ssl_ctx
 Che_version_info
 Che_wire_hdrThe wire header format It is strongly discouraged to interact with this header structure, however, it is provided for specific use cases (such as a server rejecting a session, where by definition we don't have a connection object)
 Cipv4_header_t
 Cpacket_stats
 Cplugin_structData structure of a helium plugin
 Cstats
 Ctcp_header_t
 Ctcp_option_t
 Cudp_header_t