<?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="XForms - Page 11 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=XForms&amp;p=10">1.Previous</a><br />
<a accesskey="3" href="page.php?w=XForms&amp;p=12">3.Next</a>
</p>
<p>scalability, performance, licensing, maturity, network traffic, offline capability, and cross browser compatibility. System architects should evaluate these constraints against their needs to determine potential risks and objectives.</p>

<p>Plugins like FormsPlayer and other client-side technology can have some benefits as well: because they integrate themselves into the browser, they will work with existing server architectures, can be more responsive, and require fewer server fetches.</p>

<p>The tradeoff between server-side and client plug-in</p><p>
<a accesskey="1" href="page.php?w=XForms&amp;p=10">1.Previous</a><br />
<a accesskey="3" href="page.php?w=XForms&amp;p=12">3.Next</a>
</p>

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

</card>
</wml>
