Support long running task like Cadence Temporal long running activity

long running activities are super powerful in Cadence Temporal as it allow using local machine memory and disk for executing.

However, This will not be considered into V2 of IWF. Because today’s pushing to execute task’s won’t work for long running task. So this requires to implement the polling mechanisms to execute tasks.

Workaround 1 is to use workflow instead but which means you may have to upload the large amount of states into other storage like s3

workaround 2 is combining IWF and Cadence Temporal. Use IWF to start a Cadence Temporal workflow, which just executes a long running activity.

Potentially IWF v1 can just schedule a Cadence Temporal activity and let user to execute the activity by using Cadence SDKs. But this will leak the implementation details of Cadence Temporal to IWF users so it’s considered as a “Hack” and will not be a good idea.

No files, tests, or entry points are named. Start by mapping how IWF currently schedules and executes tasks, then identify where polling would fit without exposing Cadence or Temporal implementation details. Done would mean a defined and implemented approach for long-running activities, with tests covering task polling and execution.

Written by the indexing model from the issue text.