 |
BorlandTalk.com
Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Neil P.
Guest
|
 Posted: Wed May 18, 2005 5:15 pm Post subject: Response now in que! |
 |
|
I would like to thank everyone who help me with (Response not in que?), I
would like to say, I tried everything that was told to me and used almost
everything. I did decide to go non-overlapped, for
this application.
Anyways, my application is now working and that was my goal!!!
I do have a question, why would you need WaitForSingleObject, if you can
specify a timeout for the read and write using the Read or Write
TotalTimeoutConstant?
Thank you,
Neil P.
|
|
| Back to top |
|
 |
Bob Gonder
Guest
|
| Posted: Wed May 18, 2005 6:25 pm Post subject: Re: Response now in que! |
|
|
Neil P. wrote:
| Quote: | I do have a question, why would you need WaitForSingleObject, if you can
specify a timeout for the read and write using the Read or Write
TotalTimeoutConstant?
|
Different way of doing the same thing.
Difference is if you have other things to do while waiting for file
i/o, or whether blocking is acceptable.
In your case, you really wanted to hang around and wait for the data,
so blocking was fine. (Data was more important than time, to a point)
Other people might have better things to do than wait around for
something to eventually come in, and so use overlapped with long read
timeouts, but zero or very small WaitFor timeouts. (Time more
important than data).
Also, with very long and uncertain reads, if the application decides
to close, the thread isn't blocked and can terminate readily.
|
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
