1<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
2<html xml:lang="en-US" lang="en-US" xmlns="http://www.w3.org/1999/xhtml">
3  <head>
4    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
5    <meta http-equiv="Content-Style-Type" content="text/css" />
6    <link rel="stylesheet" href="../../../../css/manpage.css" type="text/css" />
7<title>Process</title>
8  </head>
9  <body>
10<h1><CODE><a href="../../../../nn/Overview.html">nn</a>::<a href="../../../../nn/rdt/Overview.html">rdt</a>::<a href="../../../../nn/rdt/CTR/Overview.html">CTR</a>::<a href="../../../../nn/rdt/CTR/Sender/Overview.html">Sender</a>::Process</CODE> Member Function</h1>
11<h2>Syntax</h2>
12    <div class="section">
13      <pre class="definition">
14<a href="../../../../nn/Result/Overview.html">nn::Result</a> Process(
15     void
16);
17</pre>
18    </div>
19<h2>Arguments</h2>
20    <div class="section">
21<p>None.</p>
22    </div>
23<h2>Return Values</h2>
24<div class="section">Returns the result of a series of communication operations. Specifically, the following values may be returned: the value of the <a href="../../../../nn/Result/IsSuccess.html">nn::Result::IsSuccess</a> function, <CODE><a href="../../../../nn/rdt/CTR/ResultNotInitialized/Overview.html">ResultNotInitialized</a></CODE>, and <CODE><a href="../../../../nn/rdt/CTR/ResultResetReceived/Overview.html">ResultResetReceived</a></CODE>, as well as other result codes that can be returned by the UDS API. </div>
25<h2>Description</h2>
26    <div class="section">
27<p>Proceeds with communication. The actual communication takes place within this function.</p><p>This function must be called at least at intervals of each game frame (must be less than 50 msec) until the application calls <a href="../../../../nn/rdt/CTR/Sender/Finalize.html"><CODE>Finalize</CODE></a>. Applications must call this function at intervals of at least once every game frame. In scenarios where real data is sent and received, you can sometimes improve the sending/receiving performance by calling this function several times in a row. Although a single call to this function will only send about 1400 bytes at most, you can send more data than this by using <a href="../../../../nn/rdt/CTR/Sender/Send.html"><CODE>Send</CODE></a> to write a large amount of data to the RDT library's internal send buffer, then calling this function multiple times. See the <CODE>ServerClient</CODE> sample demo for more specific details about settings. Do not call other member functions (such as <a href="../../../../nn/rdt/CTR/Sender/Send.html"><CODE>Send</CODE></a>) while this function is running. In that case, behavior is not guaranteed. State transitions of <CODE>Sender</CODE> instances are also handled within this function.</p><p>Depending on the state of communications, <CODE><a href="../../../../nn/uds/CTR/ResultBufferIsFull/Overview.html">nn::uds::CTR::ResultBufferIsFull</a></CODE> might also be returned. When this happens, the outgoing data has been lost by the UDS layer but the RDT will check if the appropriate data has arrived and will resend the data if it cannot verify arrival, so you can safely ignore when <CODE><a href="../../../../nn/uds/CTR/ResultBufferIsFull/Overview.html">nn::uds::CTR::ResultBufferIsFull</a></CODE> is returned by this function.</p><!-- write here --></div>
28<h2>Revision History</h2>
29    <div class="section">
30      <dl class="history">
31        <dt>2011/05/12</dt>
32<dd>Added mention that you can ignore <CODE>ResultBufferIsFull</CODE>.<br />
33        </dd>
34        <dt>2010/06/14</dt>
35<dd>Initial version.<br />
36        </dd>
37      </dl>
38    </div>
39  <hr><p>CONFIDENTIAL</p></body>
40</html>