From: Vladislav Vaintroub
Date: November 19 2010 11:48am
Subject: RE: bzr commit into mysql-5.5-runtime branch (davi:3186) Bug#54790
List-Archive: http://lists.mysql.com/commits/124426
Message-Id: <00d401cb87df$a197d490$e4c77db0$@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit



> -----Original Message-----
> From: Davi Arnaut [mailto:davi.arnaut@stripped]
> Sent: Friday, November 19, 2010 12:03 PM
> To: Vladislav Vaintroub
> Cc: commits@stripped
> Subject: Re: bzr commit into mysql-5.5-runtime branch (davi:3186) Bug#54790

Hi Davi

> Hi Vladislav,
> 
> On 11/19/10 6:01 AM, Vladislav Vaintroub wrote:
> 


> The Winsock documentation says that after a I/O is canceled on a socket,
> the socket is left in a undefined state. It can only be closed after that.

 I would like to have a URL to that documentation.

>

> > end up with WaitForSingleObject in an optimized version.
> 
> Asynchronous I/O is nice and all, but its not viable to change the
> server design to adapt to the pattern of overlapped I/O. We should be
> looking for alternative that fit our pattern, not the other way around.

The only thing we can have is poll()..Everything that can come from Unix  is poll(), it does not have anything else (ok , it can
have good poll like epoll and bad poll like select)  and but  there is no good poll on Windows and will not ever be.

> I actually like asynchornous I/O and I'm a big fan of completion ports.
> Most of my projects which start from zero are based around asynchronous
> event loops. But they don't quite fit the MySQL I/O model. They were
> designed for other type of applications.

I was not talking real async IO, merely as a tool to emulate interruptible,  and timeout-able blocking socket operation. As I
understand we need that only, and poll() is also a tool and it is not a fact  it is a good one.

> Regards,
> 
> Davi