Async states support

[Google Code Exporter]

What steps will reproduce the problem?
1.Send email and act upon response
2.Wait until eta or for a delay
3.

What is the expected output? What do you see instead?
I would like to setup asynchronous states.

What version of the product are you using? On what operating system?


Please provide any additional information below.

Original issue reported on code.google.com by [e-mail] on 6 May 2011 at 4:12

[Google Code Exporter]

I have prototyped this sort of thing, but have not yet put it into the trunk. 
There are a few issues around permissions. It is most straightforward to simply 
put a /fantasm/fsm/MyMachine/?... url into an email, but then only developers 
can respond to email links. Supporting things like eta/timeout etc. requires 
some additional infrastructure.

Would a simple developer-only email suffice in the short term?

Original comment by [e-mail] on 6 May 2011 at 5:33

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[Google Code Exporter]

Here's another possibility:

states:
  - name: s1
    action: s1_action
    transitions:
      - event: ok
        to: s2
        async: true # tells Fantasm not to require an event from the action
  - name: s2
    ...

def s1_action(self, context, obj):
  async_token = self.get_async_token('ok')
  send_custom_email_with_custom_link_that_links_to_handler_below_and_passes_async_token(async_token)
  return null
  # fantasm would do whatever it needed to do to pause the machine - e.g., a pull queue

...

def some_custom_non_fantasm_handler(request):
  # custom validation/authorization here
  async_token = request.params['token']
  fantasm.continue_machine(async_token)
  # fantasm would reinflate and invoke the machine


The developer could possibly get async tokens for a number of transitions, so 
that they could put many different links in the email and let the user choose 
the transition ("ok", "cancel", etc.). Using this technique, the email, text 
message (or whatever) would be completely customizable by the developer.

Original comment by [e-mail] on 7 May 2011 at 4:28

[Google Code Exporter]

You're right - a pull queue wouldn't be appropriate here. I'm just looking for 
any excuse to use them!

Original comment by [e-mail] on 7 May 2011 at 5:28

[Google Code Exporter]

What is the status of this ?

It looks interesting, but I'd like to include some manual step where a user 
should enter data.

Original comment by [e-mail] on 6 Apr 2012 at 2:35

[Google Code Exporter]

Nothing currently under development, but your post has given me a chance to 
think some more about this would be implemented....

Original comment by [e-mail] on 9 Apr 2012 at 4:57

[Google Code Exporter]

We also need to make sure a link can only be clicked once - we don't want 
copies of the machine running at the same time. fantasm.continue_machine(...) 
could take care of that i guess. How do you see the pull-queue being used in 
pausing the machine? I would have thought the existing fan-in serialization 
would suffice.

Original comment by [e-mail] on 7 May 2011 at 5:16