<div>
Distributing web pages is not a heavy duty because you're <br />
probably distributing your pages over a telephone line or<br />
ISDN. Even if you use your Personal WebServer on a 'fast' isdn line, your PC will be eating out of its nose. A 'real' webserver is much faster, but you need at least a 2 MB connection to wake <br />
a 'real' server up. <br />
<br />
IIS is great if you use Frontpage for your webauthoring.<br />
Especially IIS 3.0 (with the active server pages) is great<br />
but Windows NT is strongly recommended because PWS doesn't<br />
support connecting to ODBC sources very well.<br />

</div>


Distributing web pages is not a heavy duty because you're
probably distributing your pages over a telephone line or
ISDN. Even if you use your Personal WebServer on a 'fast' isdn line, your PC will be eating out of its nose. A 'real' webserver is much faster, but you need at least a 2 MB connection to wake
a 'real' server up.

IIS is great if you use Frontpage for your webauthoring.
Especially IIS 3.0 (with the active server pages) is great
but Windows NT is strongly recommended because PWS doesn't
support connecting to ODBC sources very well.


<div>
thanks to rpabst as well<br />

</div>


<div>
<div class="content wysiwyg-content">
Anybody has a feel on how many connections the MS-Personal Server can reasonably support b4 performance degrades..?<br />
<br />
Also, does IIS2.0 already has frontpage-extension built in?
</div>
</div>


Anybody has a feel on how many connections the MS-Personal Server can reasonably support b4 performance degrades..?

Also, does IIS2.0 already has frontpage-extension built in?

General Question on robustness of Ms-Personal Server

Web development includes all aspects of presenting content on intranets and the Internet, including delivery development, protocols, languages and standards, server software, browser clients, databases and multimedia generation.