Here are the classes, structs, unions and interfaces with brief descriptions:

app	What we know about an app
client	Everything that a client needs to function
client_cb	Information necessary to fire a callback
client_sub	Information about the client's subscription to an event
event	Events are stored in a prefix tree for fast, nice lookups
evs_on_info	Contains all the fields necessary to send a callback to a client about a subscription
protocol	What a protocol needs to route messages around
protocol_frames	Some protocols (HTTP, looking at you) need a few frames types depending on the type of client they're immediately sending to, so those possiblities are stored here and exposed to all protocols
protocol_headers	For holding HTTP headers
protocol_heartbeat	Useful information about heartbeat timings
qev_cfg	A configuration option that can be parsed in a config file
qev_cfg_val	The default values for the values
qev_cfg_valptr	Where the values of the options live
qev_client	Contains all of the information needed for quick-event to have a functioning client
qev_flags	Any flags associated with a client
qev_http_request	Holds information about a parsed HTTP response
qev_stats_threshold	For determining if something should be alerted on
subscription	Events are what are located at the paths, whereas subscriptions are what are located at ev_path + ev_extra (ev_extra may == ""), and these are what you can actually broadcast and send events to