updating project installation instruction
return all busses

- created a new rout to return all busses under ‘riob.us/all'
- now we receive, from child process, the object that represents the
whole dadosabertos parsed json.
updating intervalTime and sending json to parent

- intervalTime can now be changed on our JSON configuration file and
our code will change it on ‘setInterval()’.
- sending the exact json parsed from dadosabertos to parent thread so
it can outputs it on its rest interface.
working with winston logging library
also sending a hash of bus order to parent thread
users can now query for bus orders

- making a request to ‘riob.us’ with the paramater ‘ordem=<bus order>[,
<bus order>]’ will add these busses to the json we send our response.
At most 10 bus orders can be queried at a time.
- making a request with ‘riob.us/ordem/:busOrder’ will get you a
response with at most 10 bus orders.
- rerouted ‘riob.us/:busLine’ to ‘riob.us/linha/:busLine’.
- lastUpdate isn’t an attribute of ‘data’ or ‘json’ anymore. it is a
4th attribute in the message that comes from child process.
added timeout time for the server request timeout
added timeout callback function on request

as we don’t want to keep sending requests when we don’t get a response.
Now we only send a request in 2 situations. 15 seconds after we receive
a response or 15 seconds our request times out.
we also read the ‘timeout’ from the JSON configuration file.
As we can’t now beforehand when will be out next request, the
‘setInterval()’ function has been replace for ‘setTimeout()’. We also
always keep track of the setTimeout identifier (a call to setTimeout,
returns an identifier for the function called by it).
we also consider a request’s timeout as a bad situation. so we don’t do
anything more than scheduling the next request when the timeout happens.
ignoring .log files on git
fixing port value
fixing multiple sockets hang up on remote crash

- when remote server crashes, we were getting multiple ‘socket hang
up’s. now i have figured out a way to close the connection, and treat
the respective consequences of closing it, when the remote server
crashes on our request.
- added an http status code 302 log case on response.
Merge branch 'master' into node.js-dataGrabber

Conflicts:
	riob-us/dataGrabber.js
	riob-us/server.js
Merge branch 'node.js-dataGrabber'

Conflicts:
	riob-us/dataGrabber.js
	riob-us/server.js