[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[Libevent-users] Should my code be able to deal with EAGAIN?
- To: libevent-users@xxxxxxxxxxxxx
- Subject: [Libevent-users] Should my code be able to deal with EAGAIN?
- From: Jasper Siepkes <siepkes@xxxxxxxxxxxxxxxx>
- Date: Fri, 21 Jun 2019 16:14:51 +0200 (CEST)
- Authentication-results: smtp.serviceplanet.nl; auth=pass smtp.auth=siepkes@xxxxxxxxxxxxxxxx smtp.mailfrom=siepkes@xxxxxxxxxxxxxxxx
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: libevent-users-outgoing@xxxxxxxx
- Delivered-to: libevent-users@xxxxxxxx
- Delivery-date: Fri, 21 Jun 2019 10:22:32 -0400
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=serviceplanet.nl; s=alpha; t=1561126492; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=uFzOWmFaAFi6dnqlD+LeExSTQZRgI5laYsnU+hZg338=; b=H8WRrUp3/oCnidMXs3JcxnBLvFb/MghfXVe6w6w1+s/cL/WjgPjFtxZ85Rh5xRN2COpo7r /WlmS5WEeCxYEnqRCNEe1oyQpO55F4pdBvOMZVD3mpEDXdD9ehiQXVTA7d6D/AEZ2CiDw9 RuIkAV2UKC2seqy5IUuYME3CA90qjqkE/hsHCbv4qCpZTHzyUO95qRdg9RFiKxNHW3FEc7 6w8aTnJCFvmdDCJMwepKAMX2oQXV30IuVaVTWUNOBV4m64bJO+Hf2FOdieRyI6uu+Xb+Mf LlZElPxKDiF/hsJO9/NiAdPxs/eFa3/5/mzTTptUTr62cSetHgPrEBdhsPaFcw==
- Importance: Medium
- Reply-to: libevent-users@xxxxxxxxxxxxx
- Sender: owner-libevent-users@xxxxxxxxxxxxx
Hi!
I'm a bit confused about how libevent looks at EAGAIN. From what I can tell is that some event base implementations deal with EAGAIN themselves and will never return EAGAIN as an error. However other backends do seem to return EAGAIN as an error. The "A low-level ROT13 server with Libevent" example on http://www.wangafu.net/~nickm/libevent-book/01_intro.html seems to take into account libevent could return EAGAIN but from what I can tell that documentation might be a bit dated?
Should I as a developer always consider that EAGAIN might be returned? Or should it never be returned by libevent and be handled in the event base?
Kind regards,
Jasper
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxx with
unsubscribe libevent-users in the body.