vortex_event_get_channel vortex_event_get_conn vortex_event_get_ctx vortex_event_get_encoding vortex_event_get_frame vortex_event_get_msgno vortex_event_get_name vortex_event_get_profile_content vortex_event_get_server_name vortex_event_get_type vortex_event_mask_add vortex_event_mask_enable vortex_event_mask_free vortex_event_mask_is_set vortex_event_mask_new vortex_event_mask_remove vortex_event_ref vortex_event_unref vortex_pull_cleanup vortex_pull_init vortex_pull_next_event vortex_pull_pending_events vortex_pull_pending_events_num vortex_pull_set_event_mask VortexEvent VortexEventMask VortexEventType

axl_bool vortex_pull_init ( VortexCtx *  ctx  )  Activates the pull based event notification. This interface allows single threaded applications to better interface with vortex API. Due to is threading nature, this pull API allows single threaded design to "fetch" or "pull" pending events rather receiving a notification through a handler. Once the PULL API is enabled, no async handler will be called. Async handlers configured will be ignored. A proper activation sequence is described in the following example: VortexCtx * client_ctx; // create an indepenent client context client_ctx = vortex_ctx_new (); // init vortex on this context if (! vortex_init_ctx (client_ctx)) { printf ("ERROR: failed to init client vortex context for PULL API..\n"); return axl_false; } // now activate PULL api on this context if (! vortex_pull_init (ctx)) { printf ("ERROR: failed to activate PULL API after vortex initialization..\n"); } // do some work and fetch events with vortex_pull_next_event To stop library function, including PULL API, the usual function must be used: vortex_exit_ctx