Re: Problem with WaitCommEvent in thread

Article View: borland.public.cppbuilder.nativeapi

Article #10264

Back to borland.public.cppbuilder.nativeapi Previous Next

#10264

From: Martin Nijhoff
Date: Tue, 11 May 2004 12:58

14 lines
1306 bytes

> Wont work. You must use overlapped I/O for this.

Can you elaborate on that?

Non-overlapped I/O with a second thread for reading/error checking should do
the same as overlapped I/O with a single thread, shouldn't it?

What would be the advantage of using overlapped I/O instead of
non-overlapped I/O? My application doesn't receive data while transmitting
data and vice versa.

Regards,

Martin Nijhoff

Technical Details

Message-ID: <40a0ce04@newsgroups.borland.com>

Path:

arc1-ca.pugleaf.net!controlnews3.google.com!news1.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail

References: <40a092fd$1@newsgroups.borland.com> <40a0b26b@newsgroups.borland.com>

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10cc67,4298e6c7d8d30497
X-Google-Attributes: gid10cc67,public
From: "Martin Nijhoff" <dont@mail.me>
Newsgroups: borland.public.cppbuilder.nativeapi
References: <40a092fd$1@newsgroups.borland.com> <40a0b26b@newsgroups.borland.com>
Subject: Re: Problem with WaitCommEvent in thread
Date: Tue, 11 May 2004 14:58:49 +0200
Lines: 16
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
NNTP-Posting-Host: 80.100.129.156
Message-ID: <40a0ce04@newsgroups.borland.com>
X-Trace: newsgroups.borland.com 1084280324 80.100.129.156 (11 May 2004 05:58:44 -0700)
Path: arc1-ca.pugleaf.net!controlnews3.google.com!news1.google.com!news.glorb.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail

Reply to Parent Message