On Fri, Jun 27, 2014 at 2:21 PM, Harald Oehlmann <harald.oehlmann@elmicron.de> wrote:
Am 27.06.2014 14:02, schrieb Alexandre Ferrieux:
> On Fri, Jun 27, 2014 at 11:25 AM, Harald Oehlmann
> <harald.oehlmann@elmicron.de <mailto:harald.oehlmann@elmicron.de>> wrote:
>     So thats what this piece of text tries to express:
>     "I/O primitives advance the state machine by one step".
> OK. Now you have clarified the issue with blocking/nonblocking I/O, I
> suggest to rephrase it this way:
> ----------------------
> In eventloop mode, the state machine of a (possibly multiple-address)
> async connection proceeds within an internal callback."
> In non-eventloop mode, it proceeds whenever a channel operation is
> attempted on the socket:
>       - nonblocking I/O and [fconfigure] will advance it by one step
> (i.e. do whatever is doable without waiting)
>       - blocking I/O will advance it to completion, in essence meaning
> "switch back to synchronous connect, and in case of success, do the
> blocking I/O I asked for"
> -----------------------
> Reactions ?

Thank you, Alexandre, for the proposition.

This wording is good for me.
Tip is updated. Only one detail:
As "in eventloop mode" may suggest, that there is a switch for event
loop mode, I prefer to say: "If the event loop runs"...

Do you like the updated Tip ?

Suits me :-)
Thanks !