47 lines
1.3 KiB
HTML
47 lines
1.3 KiB
HTML
|
<html>
|
||
|
|
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type"
|
||
|
|
content="text/html; charset=iso-8859-1">
|
||
|
|
<meta name="GENERATOR" content="Microsoft FrontPage Express 2.0">
|
||
|
|
<title>Buffer Flags</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<body>
|
||
|
|
|
||
|
|
<h1>Buffer Flags</h1>
|
||
|
|
|
||
|
|
<hr>
|
||
|
|
|
||
|
|
<table border="1">
|
||
|
|
<tr>
|
||
|
|
<td><code>KCommBufferFull&</code></td>
|
||
|
|
<td>Full buffering means that the comms server will
|
||
|
|
always attempt to allocate enough memory to satisfy any
|
||
|
|
reads or writes in a single copy.<p>When a port is opened,
|
||
|
|
the default is full buffering</p>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
<tr>
|
||
|
|
<td><code>KCommBufferPartial&</code></td>
|
||
|
|
<td>Partial buffering means that the comms server will
|
||
|
|
allocate a static buffer and use partial copies to
|
||
|
|
transfer data to the serial driver. </td>
|
||
|
|
</tr>
|
||
|
|
</table>
|
||
|
|
|
||
|
|
<h5>Note</h5>
|
||
|
|
|
||
|
|
<p>The default of full buffering is nearly always going to be the
|
||
|
|
quicker option, as only a single client-server data transfer is
|
||
|
|
ever needed. The mode should not be changed by an application
|
||
|
|
without a very good reason (such as memory constraints) otherwise
|
||
|
|
performance is liable to suffer</p>
|
||
|
|
|
||
|
|
<h5>See Also</h5>
|
||
|
|
|
||
|
|
<p><a href="file:///P:/Opx/CComms/DOCUME~1/comm.htm#Mode">CommMode</a>,
|
||
|
|
<a href="file:///P:/Opx/CComms/DOCUME~1/comm.htm#SetMode">CommSetMode</a></p>
|
||
|
|
</body>
|
||
|
|
</html>
|