Re: timeouts, select, dispatch

[Alain Magloire]

> 
> 
> --5I6of5zJg18YgZEa
> Content-Type: text/plain; charset=iso-8859-1
> Content-Disposition: inline
> Content-Transfer-Encoding: quoted-printable
> 
> > Yes, it keep tracks, You will have to reissue the same command.
> > Actually reissuing another command will return EBUSY or something,
> > since the "TOP 1 0" is not complete, the code will not let you do things =
> like
> > "RET 1" until the "TOP .." finish.
> 
> Excellent ! I better understand your statement that this causes 60%
> code overhead :-)
> 

Yes, keeping the state is the cause of the code bloating.
And it is even worst when doing it for IMAP4.
NOTE:
- Non-blocking will work for POP3, it was tested
  but I've never test it with IMAP4.

This is why I'm proposing to drop this feature, actually
I'm suggesting to drop 2 features:

- support for non-blocking I/O
- support for thread-safe

Pushing this out of the library in to userland.

But in will not happend tomorow 8-)