Pseudo-conversations
Simple solution in early TP system products
A conversational transaction interacts with its user during its execution
This is a sequential workflow between user & server.
Since this is long-running, it should run as multiple requests
Since there are exactly two participants, just pass the request back and forth
- request carries all workflow context
- request is recoverable, e.g. send/receive is logged or request is stored in shared disk area
This simple mechanism has been superceded by queues and general-purpose workflow systems.