1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2<html xmlns="http://www.w3.org/1999/xhtml">
3<head>
4<meta http-equiv="Content-Type" content="text/html; charset=windows-1252" />
5<meta http-equiv="Content-Style-Type" content="text/css" />
6<title>WFS_SetServerSync</title>
7<link rel="stylesheet" href="../../css/nitro.css" type="text/css" />
8</head>
9<body>
10
11<h1>WFS_SetServerSync <img src="../../image/NTR.gif"><img src="../../image/TWL.gif"></h1>
12<h2>Syntax</h2>
13
14<dl>
15  <dd>
16<code>#include &lt;nitro/wfs.h&gt;</code><br />
17  <br />
18  <code>void WFS_SetServerSync(WFSServerContext *context, int bitmap);</code><br />
19  <br />
20  </dd>
21</dl>
22<h2>Arguments</h2>
23<table border="1" width="100%">
24  <tbody>
25    <tr>
26      <td style="width:13%"><em><strong>context</strong></em></td>
27      <td style="width:87%">Pointer to the <CODE>WFSServerContext</CODE> structure.</td>
28    </tr>
29    <tr>
30      <td style="width:13%"><em><strong>bitmap</strong></em></td>
31      <td style="width:87%">AID bitmap for the children (clients) to synchronize the responses for.<br />
32                            No response synchronization will be done if 0 is specified. (This is the default behavior.)<br />
33                            The lowest-order bit is always ignored.</td>
34    </tr>
35  </tbody>
36</table>
37<h2>Return Values</h2>
38<p>None.</p>
39
40<h2>Description</h2>
41<p>Sets the synchronization group to use when a parent (server) responds to read requests from children (clients). The WFS library assumes that the group of children (clients) specified with this function will issue read requests for the same content at the same time from the perspective of the parent (server). The library will wait to respond until all read requests have been issued from all of the children (clients) in question. Since the WFS library has excellent ability to broadcast the same content to all children, improved transfer efficiency can be expected.</p>
42<p style="color:red">
43The parent (server) will not start the response unless requests from all the specified children (clients) are in place, so be aware that certain application designs could result in a deadlock.
44</p>
45<p>
46If even one of the read requests issued by the children (clients) is different from the others, the synchronization setting will be cancelled.
47</p>
48
49<h2>See Also</h2>
50<p><code><a href="WFS_GetServerConnectedBitmap.html">WFS_GetServerConnectedBitmap</a>, <a href="WFS_GetServerBusyBitmap.html">WFS_GetServerBusyBitmap</a> <br /></code></p>
51
52<h2>Revision History</h2>
53<p>
542007/06/06 Initial version.
55</p>
56<hr><p>CONFIDENTIAL</p></body>
57</html>
58
59