making basic AWE http server (site and api) work
AWE server can receive pipeline job (script) submission via API (POST)
support GET API, implementing Read() and ReadMany() in jobController
implement queue manager (parsing jobs/tasks, manage queues of tasks/workunits)
Merge pull request #1 from wtangiit/master

AWE server APIs and queue manager
enable to parse job scripts in json format
Merge branch 'master' of github.com:MG-RAST/AWE
add workController, providing API for workunit checkout (by ID or in FCFS)
add awe-client, initial commit
awe-client can checkout workunits from awe-server via http.Get()
queue manger supporting concurrency control in workunit checkout
awe-client fetched input data from Shock and ran first workunit successfully
modify core.IO fields to facilitate data dependency handling
qmgr creates Shock node for task output by POST
Merge pull request #2 from wtangiit/master

workunit checkout, awe client, interacting with shock, and more
awe-client pushes back output to shock node
awe-client notifies qmgr work done and the latter moves possible new ready tasks to workunit queue
qmgr locates input data (shock node) for a task based on its predececor's output
add timer goroutine for updating queue; put awe-server url to conf
concurrency control for workunit status feedback