<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Super-server - Page 3 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=super-server&amp;p=2">1.Previous</a><br />
<a accesskey="3" href="page.php?w=super-server&amp;p=4">3.Next</a>
</p>
<p>handled by an already-running process).</p>

<p>Whether this delay is incurred repeatedly for every incoming connection depends on the design of the particular sub-daemon; simple daemons usually require a separate sub-daemon instance (i.e. a distinct, separate operating system process) be started for each and every incoming connection. Such a request-per-process design is more straightforward to implement, but for some workloads, the extra CPU and memory overhead of starting multiple operating system processes may be undesirable.</p>

<p>Alternatively,</p><p>
<a accesskey="1" href="page.php?w=super-server&amp;p=2">1.Previous</a><br />
<a accesskey="3" href="page.php?w=super-server&amp;p=4">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
