From 4a7d2fa4f75050545d0834613baab3afb1818a38 Mon Sep 17 00:00:00 2001 From: Linus Nordberg Date: Fri, 27 Aug 2010 14:33:15 +0200 Subject: Thinking out loud some more. --- lib/libradsec.h | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/lib/libradsec.h b/lib/libradsec.h index 9d9ee9c..5765282 100644 --- a/lib/libradsec.h +++ b/lib/libradsec.h @@ -130,15 +130,16 @@ struct rs_packet *rs_packet_receive(const struct rs_conn *conn); three different ways, from easiest to hairiest: i) Blocking i/o model: User passes NULL for the callbacks in - rs_conn_open() and the open, send and receive calls will block - until the wanted event occurs. Other events occurring while - waiting will be either silently discarded or signaled as an error + rs_conn_open(). The open, send and receive calls will block until + the desired event occurs. Other events occurring while waiting + will be either silently discarded or signaled as an error (f.ex. broken connection while sending). - ii) Simple interface with a timeout: User calls - rs_event_loop(timeout) to process pending i/o. + ii) Simple event loop interface with a timeout: User calls + rs_event_loop(timeout) to process pending i/o. Should be a good + choice for most applications. - iii) full libevent interface: TODO. + iii) Full libevent interface: TODO. */ #error "need an rs_event_loop() and more" -- cgit v1.1