1) HttpConnection object was enqueued for deletion twice in case of write-cb (read from socket)
       followed by a socket error. Use socket transfer done indication from client library to
       enqueue HttpConnection object delete.
    2) mcode_or_die remove exit from the the code, consecutive calls detect socket errors and inform
       the clients.
    3) Initiate a resubscribe/republish on paring xml failure error.
    4) Discovery client registers for write_cb when <body> of an HTML response is recieved, when
       only <header> is received(not expected) this should be considered as an error case and trigger resubscribe
       or republish. This is done by marking the write_cb.
Merge pull request #26 from Juniper/discovery-timeout-changes

    1) HttpConnection object was enqueued for deletion twice in case of ...