| FTP | The advantage of FTP is that it is a well established protocol, and is
commonly available. The down side is that it passes your user name and password in the clear.
In theory, someone could grab your user name and password, and wreak havoc with it. |
|---|
| Local/Network | This makes some assumptions about your access to the server. If
you are working in the same office that the web server exists, or you have absolutely no problem
opening up the dreaded Microsoft NetBios ports, then this would work. If your network admin
has any shred of paranoia whatsoever, this will not be an option. Alternatively, in the UNIX /
SAMBA world, this is a good option. |
|---|
| WebDAV | I dont know much about this protocol yet. I do know that it is installed
by default on Windows 2003 server, it just isn't enabled. I tried this protocol, and received
a blank listing for my troubles.
|
|---|
| RDS | Remote Data Services. It is a catchy sounding title, but when I was looking
into enabling it, there were all kinds of warnings on the Microsoft site about having to run
IIS in unsecure mode. This sounded like a bad thing. |
|---|
| Microsoft Visual SourceSafe | This might be a good solution for offices where
a lot of people are working on the server, but from my point of view, Source Safe has never been
anything but a headache when there are just a few programmers working on a project.
|
|---|
