<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
I believe Mediacom's "no server" policy serves two purposes: 1) to avoid
the bandwidth hits that might be associated with a professional server
of high capacity (hoging bandwidth) and 2) as a disclaimer so customers
can not complain when the service is down for longer then a Professional
ISP. Being a cable company it can be days before they send a tech person
to your home to fix your cable.
<p>With the above in mind, if you have a local low capacity server and
can tolerate having it down for several days on those occasions when the
cable company has a problem which requires them to send out a technician
then Mediacom is unlikely to detect or care about you running a server.
<blockquote TYPE=CITE><nobr><b>Subject: </b>[DM-MUG] Apache</nobr>
<br><nobr><b>Date: </b>Mon, 2 Apr 2007 11:19:01 -0500</nobr>
<br><nobr><b>From: </b>Ray Bowler <rbowler@mchsi.com></nobr>
<br><nobr><b>Reply-To: </b>Des Moines Mac Users Group <dmmug@dmmug.org></nobr>
<br><nobr><b>To: </b>DMMUG <dmmug@dmmug.org></nobr>
<br>I was just looking at the Apache information under the "sites" folder <br>
at root. If I keep my computer up and MCHSI allows it would this be <br>
accessible over the internet? Does anyone know what Mediacom's policy <br>
is about this?<br>
-- <br>
Ray Bowler<br>
<br>
rbowler.home.mchsi.com</blockquote>
</html>