This is something that has to change for the final interface designs. There
have been slight design changes in terms of how we think it's best to get the
file from the ballot creation application to the server. In the original
design, we assumed that a PHP script could and would do all the work of getting
the file on its own. However, since we don't know how easy or hard it would be
to get a C++ program to contact a PHP script and then simulate a user sending a
file, we thought the following process for contacting the server would be
easier:
	
	1. FileManager uploads the file to an FTP server running on the same server
	as the web site.
	2. The FileManager then calls the receive.php script on the server. The
	simple act of running this script will alert the script that a file has
	been uploaded. The script would then look in the appropriate directory on
	the server and do whatever it needs to do with the file.

This requires running an FTP server on the server. We need to make sure that's
set up along with the database as soon as possible, since it's yet another
thing we need to interact with CIS about.

In summary, the dependency between the ballot creation application and the
server now consists of two things: an FTP server and a call to the receive.php
script.