Broadcast via web api

Made the XConfig code capable of reading JSON. Might not be a perfect JSON parser but good enough. This was mainly acheived by supporting multiple terminators (specifically the comma as well as XConfig's \n). 

A stream service can specify a web API call. If the URL starts with HTTP (instead of RTMP) then do an HTTP query on the URL (with a given stream/path/broadcaster key number). This webapi to return something like:
 {"data":{"stream_url":"rtmp://some_url", "stream_name": "some-name"}}

This is the same information specified in the services.xconfig file. So the data returned in JSON is then passing to the stream startup as usual.