Sounds good to me. It's the ideal sort of thing a contributor could work on -- important but not blocking forward progress. Be sure to file a bug and mark it "Available" and "OS:Linux" if you don't want to work on it yourself. :)
On Fri, Sep 26, 2008 at 12:28 PM, Darin Fisher <[EMAIL PROTECTED]> wrote: > my initial implementation is just going to be blocking file IO for posix. > we can extend that later to either use aio_read or a thread pool or > whatever :) > i just want to unblock the port first with a basic implementation. > -darin > > On Fri, Sep 26, 2008 at 8:02 AM, Avi Drissman <[EMAIL PROTECTED]> wrote: >> >> I was discussing this with Amanda last time I was in MTV, and the problem >> with aio_* is that you can't use it asynchronously for opens and closes, >> only for reads and writes. If we want to do async opens/closes in the API, >> we have to do something else for them, and by that point there's no reason >> for having two mechanisms. >> >> a >> >> On Fri, Sep 26, 2008 at 8:57 AM, Mike Pinkerton <[EMAIL PROTECTED]> >> wrote: >>> >>> What about something like aio_read() for POSIX? >>> >>> Thanks for starting this up, I just came across yet another use for it >>> yesterday in the http file upload code. >>> >>> On Thu, Sep 25, 2008 at 9:36 PM, Darin Fisher <[EMAIL PROTECTED]> wrote: >>> > If you aren't working on a port of chromium, you can stop reading now. >>> > I wanted to send out a brief update regarding file handling in the net >>> > module. I've been making good progress on introducing a file input >>> > stream >>> > abstraction that'll serve the needs of our UpdateDataStream and >>> > URLRequestFileJob classes. (I suspect that it may come in handy in >>> > other >>> > parts of chromium as well.) >>> > Here's the bug tracking this work: >>> > http://code.google.com/p/chromium/issues/detail?id=2735 >>> > >>> > My hope is to have something out for review tonight or tomorrow. >>> > I haven't figured out how best to do asynchronous mode file IO on >>> > non-Windows systems yet. Conventional wisdom says that a thread pool is >>> > the >>> > answer. Anyways, that part is yet to come. >>> > -Darin >>> > > >>> > >>> >>> >>> >>> -- >>> Mike Pinkerton >>> Mac Weenie >>> [EMAIL PROTECTED] >>> >>> >> >> >> > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/chromium-dev?hl=en -~----------~----~----~----~------~----~------~--~---
