accept node port as argument
create simple example PhantomJS tester

PhantomJS successfully communicates with the server using two separate clients.
current tester illustrates the propagation of a commit, showing how if client1
commits, an immediate check by client2 does *not* reveal the commit, however it
does after waiting ~1s.
update README
improve example tester to illustrate latencies

now reads off the latency of a single commit to each of two clients, one that
sent it and one that received it.
create first, easy tests using PhantomJS

- test with 1 writer, many listeners
- test with different writers writing at different times, many listenres
- test with many concurrent writers who make non-conflicting updates

Also, made the server print something when it starts so that spawned process in
node can listen to it's stdout and then initiate testing. Additionally,
introduced `pause` and `play` into the Pad javascript API. It essentially
buffers updates from the server and doesn't apply them to the state, allowing
explicit simulation of concurrent modifications.
add harder tests for conflicting updates
Merge branch 'master' into phantomjs-testing

Conflicts:
	pad.go
update readme
get working on aws
ignore aws keys
Merge branch 'master' into phantomjs-testing

Conflicts:
	.gitignore
	pad.go
make work now that pad server spews BS to stdout
Merge pull request #13 from jdhenke/phantomjs-testing

PhantomJS Testing

runs tests locally to test for correctness of javascript API.
make pad server setup more scalable

- allows custom ports locally
- pad servers communicate via tcp
- updated README to reflect the new changes
- reorganized the repo a bit
include go files and key directory
refactor to json config; works locally
run remotely on aws
cleanup stdouts and readme
update readme
Update README.md