-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Conrad T. Pino wrote:
>Native Win32 handles don't have a blocking (synchronous) or (non-blocking)
>asynchronous attribute/property/flag i.e. this mode is NOT chosen at file
>open/create time. The choice is made when invoking the I/O operation by
>using either synchronous or asynchronous forms of the I/O operation. The
>same file handle will support concurrent asynchronous and synchronous I/O
>operations (provided they're invoked in the correct order or by different
>threads).
>
>Example ReadFile (either mode) & ReadFileEx (asynchronous only):
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/readfile.asp
>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/fileio/base/readfileex.asp
>
>The real challenge lies in the POSIX compatibility routines of the I/O
library
>which are in use. We need to find the library data structure that
determines
>which Win32 API call will be invoked for the next CVS I/O function call.
Well, if we could do it with POSIX functions under Windows, that would
be great for portability, but failing that, we can call anything we need
to - many of the file access functions already have Windows specific
versions in windows-NT/filesubr.c. Perhaps a function in filesubr.c
that calls ReadFileEx? I'll look into it after Larry and I finish our
discussion about whether this check is even any longer appropriate.
>Can you provide a list of functions of interest for asynchronous I/O?
I don't really care which function, as long as it will read one byte of
data asynchronously from a file descriptor.
>I only have Visual C++ 6.0 and various Borland C/C++ compilers.
>How much flexibility do we have deviating away from Visual C++ 5?
Well, fact of the matter is, I only have VC++ 6.0 too, so unless someone
who has VC++ 5.0 wants to help out, we'll have to drop support for VC++ 5.0.
Derek
- --
*8^)
Email: derek@xxxxxxxxxxx
Get CVS support at <http://ximbiot.com>!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Netscape - http://enigmail.mozdev.org
iD8DBQFAMZvILD1OTBfyMaQRAnarAKCEETtA4f1l8X+WkNzOphUBusFF9ACguKhj
NNu41Cyt4Z2/GnsHDaJYlEA=
=arcF
-----END PGP SIGNATURE-----
|
