[gambit-list] Error with iOS 5.0
mikael.rcv at gmail.com
Wed Jun 15 11:29:15 EDT 2011
Hm, what about if the harddrive is busy with higher-prioritized IO
operations. In this case I suppose the a nonblocking file read is supposed
to return with 0 bytes immediately - what do you say?
Though, I suppose there's no way to know from the OS when the drive will be
ready for making access again since there's no async-ness in the standard
file read procedure, I wonder how Gambit works in relation with that
currently (though it's really a kind of exotic situation).
2011/6/15 Alan Post <alanpost at sunflowerriver.org>
> On Wed, Jun 15, 2011 at 07:44:15AM -0400, Marc Feeley wrote:
> > and see if that eliminates the problem. Of course this makes I/O to
> files blocking, so the thread multiplexing will not work when doing I/O to
> My understanding is that for regular files, nonblocking mode is
> essentially a no-op, as regular files don't block in the way, say,
> an interactive prompt or a network socket would.
> Can someone confirm or disprove this?
> .i ma'a lo bradi ku penmi gi'e du
> Gambit-list mailing list
> Gambit-list at iro.umontreal.ca
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gambit-list