On Wed, Oct 3, 2012 at 12:54 AM, Matthew Mondor <mm_li...@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
------------------------------------------------------------------------------
Keep yourself connected to Go Parallel:
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
