> Why not just use CFile's ReadHuge()?
I doubt CFile supports overlapped I/O, but at any rate, MSDN states that this function is obsolete, and CFile::Read( ) (which maps to a ReadFile( ))
I don't see any reason not to use ReadHuge() - in fact, the name is more meaningful of what you intend, to read enormous globs of data. It is provided for backward compatibility, so by definition it is still quite valid. Not that I envisage ever having to use it.
Instead of ReadHuge( ), just issue standard read. I don't see the advantage of ReadHuge( ).
must be used instead. Anyway, I almost never use CFile, so I don't have any idea of its performance, but I'm sure anything that uses a blocking I/O would not outperform overlapped I/O.
I doubt it could, no... but then what are you going to do while waiting for
that huge file to load anyway?
You have a point on that one. The whole reason for overlapped IO is to start an IO and not wait for it to complete, but allow you to truck along and do more processing.
{:v) But it should make the system more
responsive while it loads it, I guess, using overlapped.
And you lose the point on that one. The rest of the *system* is just as responsive if your app is blocked on IO or not.
_______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
