| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | DosRead blocking |
-=> Quoting Phil Crown to James R. Cook <=-
JRC> Say, in your opinion, is it more efficient to buffer
JRC> the comm port with a thread in the program, or not to worry with it.
JRC> I've been turning that one around in my head for a couple of days and
JRC> I can't see where the overhead would be worth it ...
PC> If its a PM program I would use a thread to avoid blocking the message
PC> queue (main) thread for too long.
It's a simple text-mode app.
PC> Also by using a secondary thread you can adjust the priority. In my
PC> app the thread that reads the com port runs at PRTYC_TIMECRITICAL and
PC> all the other threads run at PRTYC_REGULAR.
But does this make a huge deal? I disremember what SIO uses for buffers,
but I would imagine that it's more than adequate.
={) James (}=
--- Blue Wave/DOS v2.30
* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)SEEN-BY: 50/99 54/99 270/101 620/243 625/0 160 640/201 711/409 410 413 430 SEEN-BY: 711/808 809 934 955 712/311 407 505 506 517 623 624 704 841 713/317 SEEN-BY: 800/1 @PATH: 106/2000 396/1 270/101 712/624 711/808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.