Erlang/OTP rest server listening for user specified routes.
Communicating in json.
. start.sh . stop.sh rest_server_app :: OTP application
route_handler :: Normal erl file
battle_ship :: Normal erl file
tcp_listener :: OTP gen_server
tcp_reply :: OTP gen_server
commands :: Normal erl file
OTP design (and a lot of the code) taken from:
http://erlangcentral.org/wiki/index.php?title=Building_a_Non-blocking_TCP_server_using_OTP_principles