🚀 go-pugleaf

"mr. Burns" <mr._burns@web.de> wrote in message
news:44e4affa@newsgroups.borland.com...

> Up to now I did not really understand what the GetOverlappedResult()
> function is for. I just want to let read my client a certain No. of bytes
and
> if this is not finsihed e.g. in 20 seconds my program should show an error
> message. But in this 20 seconds I want to do something useful and not
> block my application.

Then I suggest you move your named pipe code into a worker thread.

> Lets say I use now the WaitForSingleObject() function. You said that
> the overlapped ReadFile function signals the event when reading is
finished.

Yes.

> Then I just have to code e.g. ShowMessage(InBuf) in the
> WAIT_OBJECT_0 case to catch the complete transmitted data,
> or not?

Yes.  But you still need to know how many bytes are actually in the buffer
in order to process it correctly.

> So for what now is the GetOverlappedResult()  function?

To know the number of bytes that were actually read.

> When do I have to call it?

When the overlapped operation has finished, and the event has been signaled.

> How many bytes maximum I can transmit using named pipes? Is there any
limit?

There is no limit.  However, WriteFile() will return the number of bytes
actually written each time, so that you can adjust your writing accordingly
if there is still pending data that needs to be written each time.  For
instance, if you are sending 100 bytes and only 50 are written, you have to
call WriteFile() again to send the remaining 50 bytes.


Gambit