<?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="Comet (programming) - Page 12 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Comet_(programming)&amp;p=11">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Comet_%28programming%29&amp;p=13">3.Next</a>
</p>
<p>1.1 specification, which states "this specification... encourages clients to be conservative when opening multiple connections". Therefore, holding one connection open for real-time events has a negative impact on browser usability: the browser may be blocked from sending a new request while waiting for the results of a previous request, e.g., a series of images. This can be worked around by creating a distinct <a href="page.php?w=hostname">hostname</a> for real-time information, which is an alias for the same physical server. This strategy is</p><p>
<a accesskey="1" href="page.php?w=Comet_(programming)&amp;p=11">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Comet_%28programming%29&amp;p=13">3.Next</a>
</p>

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

</card>
</wml>
