+ *
+ * In "polling" state dump mode, the application or library is responsible
+ * for periodically invoking side_statedump_run_pending_requests(). This
+ * mechanism is well-suited for single-threaded event-loop driven
+ * applications which do not wish to introduce multithreading nor
+ * locking-based synchronization of their state.
+ *
+ * In "agent thread" state dump mode, libside spawns a helper agent
+ * thread which is responsible for invoking the state dump callbacks
+ * when requested by the tracers. This mechanism is well-suited for
+ * instrumentation of multi-threaded applications which rely on
+ * locking to synchronize their data structures across threads, and
+ * for libraries which have no control on application event loops.