Support piping of config files addressing.

This addresses issue #43 . As discussed in that issue thread, the next phase will be integrating sending of configs/content to the workers via IPC, but we could probably use a fresh issue for that. Also, the owner of parsons said he could not yet add in my change[implementing json parsing from a file pointer], because he is working on stuff in dev and planning on rolling out that feature later in October instead of right now. This is why this code implements file content extraction into a string and then the json gets parsed from it.
There would be a difference in that the buffer already had content ie 1024 chars and once no content is read in, (r == 0) returns immediately due to EOF. In that case we need to free the 1023 unused bytes. If content had actually come in at EOF, (r == 0) but a couple of bytes are used up.