At home, I use SVN with file protocol using a shared drive. Thus I can easily update from any of the computers in my house as long as the network and the file server are turned on. The documentation says they recommend against using file for production use, but I don't see why: It works fine for me.
At the office, we use SVN with http protocol, so we can access from anywhere you can reach the Internet.
SVN also has a custom protocol. We tried that briefly but there were no obvious advantages over using http.
As to clients: At home I use Subcommander for routine operations. If Subcommander is capable of creating new libraries and doing some other administrative functions, I don't know how to do it, so I fall back to command-line Subversion for admin stuff.
At the office we mostly use the Eclipse client. I use Tortoise for browsing.
The moral of the story being that there are lots of choices.
I'm not aware of any version control system that uses FTP, but I would think HTTP accomplishes the same thing. Of course you may have requirements I'm not aware of.