Re: Async I/O support attempt for Chromium

Alan Matsuoka <[email protected]>
Newsgroups gmane.comp.graphics.chromium.devel
Message-ID <1089554611.23928.15.camel@localhost>
On Sat, 2004-07-10 at 23:23, Mike Houston wrote:
> I think I can get the SDP layer kicked over to Asynchronous I/O (AIO), 
> but I only know how to do this for Linux.  Does anyone out there know 
> how to get documentation on AIO for other Unix systems? 
So far as I know, there aren't any. Ben Lahaise wrote the original code
for AIO and some of the docs and I wrote the manpages for the rest. (It
helped that his office was next door to mine). I'm not aware of any
other docs. 
 > In theory, this 
> should also work for tcp and allow a cleaner way to handle non-blocking 
> i/o without resulting to threads.
> 
> Setting the sockets to O_NONBLOCK doesn't seem to help as the sockets 
> run out of buffer space quickly and revert back to blocking.  e.g. write 
> returns E_WOULDBLOCK.
> 
> Once I can get crserver to stop segfaulting, I can continue to work on 
> this in my spare time.
> 
> -Mike
> 
> 
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
> digital self defense, top technical experts, no vendor pitches, 
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Chromium-dev mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/chromium-dev
-- 
Alan Matsuoka
Global Professional Services
Red Hat Canada, Ltd
mailto:[email protected]



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.