#include <avis/elvin.h>
Typically a client creates a connection (elvin_open()) and then subscribes to notifications (elvin_subscribe()) and/or sends them (elvin_send()). For applications that create subscriptions, the usual model is to connect, subscribe and then call elvin_event_loop() to dispatch incoming notifications.
Elvin client connections are single-threaded, and are designed to be driven by a thread calling elvin_event_loop(). Multi-threaded applications should use elvin_invoke() to safely invoke operations in the event loop thread.
bool Elvin::polling |
time_t Elvin::last_receive_time |