Animation - Contingent Requests Pattern

Description.  A party X makes a request to another party Y. If X does not receive a response within a certain timeframe, X alternatively sends a request to another party Z, and so on.

Case 1: Response to contingent request arrives before reponse to original request.

The requestor (i.e. the "customer" in the animation) sends a first request to its supplier of choice ("supplier 1").
A response is expected within 5 seconds. The response does not arrive on time, and thus the customer sends a request to another supplier ("supplier 2"). Supplier 2 responds in a timely manner and the customer consumes this response. Later on, the response to the original request arrives from supplier 1, but the customer ignores it since it has already proceeded with supplier 2's response.

Case 2: Response to original request arrives before reponse to contingent request.

Same as previous case, but while supplier 2 is processing the "contingent" request, supplier 1 responds to the original request. The customer decides to process supplier 1's response, and subsequently ignores the response from supplier 2.


Previous: Multi-responses Pattern Animation Next: Atomic Multicast Notification Pattern Animation Up: List of Animations

Site created and maintained by:
Alistair Barros, SAP, Brisbane Research Centre, alistair.barros at sap.com
Marlon Dumas, BPM Research Group, Queensland University of Technology, m.dumas at qut.edu.au
Arthur ter Hofstede, BPM Research Group, Queensland University of Technology, a.terhofstede at qut.edu.au
Part of a joint initiative by SAP and Queensland University of Technology, co-funded by Queensland State Government.
This page was created on the basis of an open-source template designed by www.404creative.com