Client need to receive a JOB_CREATED from server before submitting a new job #77
Description
We are currently locking in client.do() to avoid a race condition when submitting jobs. We do not have anything to identify the submitted job with when receiving a JOB_CREATED response from the server so multiple simultaneous job submissions need to happen on separate connections if we don't want to lock.
Previous discussion on this can be found in #75
Protocol reference: http://gearman.org/protocol/