title: Eliminate the long polling of the external tasks in Camunda to the process engine
body: <p>I'm trying to eliminate the long polling method of the camunda process engine to notify the external tasks client.</p>
  <p>My first attempt is to use the ExecutionListener class and his method notify at the start event of an activity in my bpmn to send a message to a AWS SQS queue with the external task id at the payload.</p>
  <p>After the sending of the message my External Task will pull the message from the queue, process it and send a response via another AWS SQS queue to the process engine with the external task id in the payload.</p>
  <p>At the receiving of the response message from the queue my process engine will capture the external task id from payload and complete the external task activity. Another way would be my external task make a post request at the [external-task/{ext-task-id}/complete].</p>
  <p>My question is if there is another best method in order to achieve the decoupling of the process engine and the external tasks and how can I programmatically capture the external task id.</p>
  <p>Thanks!</p>