Cable architecture is such that intensive uploading will penalize
performance for others on the same segment. It is for this reason there are
restrictions of one sort or another on servers lodged on subscriber's
systems. A private ftp server used to take some smallish files from time
to time while at a remote location, office or while traveling, is no
problem, though some cable operators will even object to such usage.
Aside from the problems inherent in public ftp or web servers --legality of
material offered and bandwidth usage, there are also others. For example,
I know of a case where a fellow had a mail server that went kaflooey and
swamped the cable system with all sorts of garbage.
Cable architecture was conceived at a time long before just about anyone
could set up a server, long before there was mp3, long before file sizes
were measured in megabytes rather than kilobytes. Given those changes,
and the competition now arising from adsl and satellite in the future, cable
will have to change, too. But, this is not a trivial procedure. In any
case, we'll have to live with what we have today for the next few years at
> > He seems to be good of charter.net, or one of his right hand men.
> Mind you,
> > all the cable operators are faced with abuses, especially those who
> think it is
> > their right to run a server from their system, even if it will make it
> > negatively the performance of othes and hog the finite amount of
> > available both within the cable system and on the internet itself.
> > -er
> But for crying out loud, the original post said: "I am having the
> RoadRunner service installed in my house in a couple of weeks and would
> like to set up a FTP server so that I can access the files from my
> computer at work."
> So what's the difference in bandwidth usage between having an ftp server
> at work, and running a client at home to transfer files to work, as
> opposed to having a single password protected login from home and being
> able to be physically at work and transfering files from your home to
> work (and vice-versa)?
> The file(s) get transferred either way, so the only difference is having
> the ftp server at home is a great convenience and not having it is a big
> pain in the ass (assuming lots of work at home is done, and so lot's of
> files are transferred).
> There's no extra bandwith being wasted, period. In fact, some might be
> saved because he'll only transfer what he needs, as opposed to
> transferring *everything* before leaving for work, "just in case."
> Sent via Deja.com http://www.deja.com/
> Before you buy.