[Ecls-list] EPIPE and C errors

Juan Jose Garcia-Ripoll juanjose.garciaripoll at gmail.com
Wed Nov 28 14:37:56 UTC 2012


On Wed, Oct 3, 2012 at 12:54 AM, Matthew Mondor <mm_lists at pulsar-zone.net>wrote:

> Unfortunately there's still no way to differenciate a timeout error
> (EAGAIN) from a broken pipe one (EPIPE) when using STREAM-ERROR.
> However, because of the design of the system (in HTTP we first read a
> request then answer, so it's not highly bidirectional, and blocking
> mode is used with threads in this case to allow CPU-bound applications,
> so EAGAIN/EWOULDBLOCK will not occur for output).  As a result, EPIPE
> will only occur for output (treated like end-of-file) and EAGAIN for
> input (treated like input timeout), so in this case the problem is
> solved for now.
>

A feature request has been added, to remind me of this.

http://sourceforge.net/p/ecls/feature-requests/14/

Feel free to add to it.

Juanjo

-- 
Instituto de Física Fundamental, CSIC
c/ Serrano, 113b, Madrid 28006 (Spain)
http://juanjose.garciaripoll.googlepages.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20121128/5a26d06b/attachment.html>


More information about the ecl-devel mailing list