On Thu, Nov 09, 2006 at 02:08:11PM -0700, [EMAIL PROTECTED] wrote: > Chanz wrote: > > I know in the Python/Twisted world there is a belief that > > event level programming on file i/o is a waste - that you might just as > > well do normal blocking opens/read/write/close since the kernel will do > > most of the heavy lifting. Does any one know if this is true? > > I use Twisted, and just this week and last week I've been wishing that Twisted > would allow me to specify deferred file I/O so that my numerous and > time-consuming disk I/O operations would not block CPU-only operations.
amen! Unfortunately the APIs for doing non-blocking file I/O are much less portable (each OS has their own, if any) than for network I/O which is part of the reason you don't often see it pre-wrapped and available in a high level language. -greg _______________________________________________ p2p-hackers mailing list [email protected] http://lists.zooko.com/mailman/listinfo/p2p-hackers
