On Fri, 2014-08-15 at 14:43 +0000, Nick Dedekind wrote:
> This was a condition enforced in the first iteration of prompt sessions.
> It will be removed later, once the services support parallel processing
> of prompt requests.
We do this today. Which is, ironically, the only way it works as the
user can click the pay button again and we do a second prompt :-)
> The payments helper should be putting password prompts/etc as part of
> it's prompt providers, as far as I'm aware, there shouldn't need to be
> any app context switching when dealing with prompt sessions.
There would be if you had something like a password manager and you
needed to go look up the password and come back to the dialog. Or
perhaps for 2fa you'd go to authenticator.
On Fri, 2014-08-15 at 14:43 +0000, Nick Dedekind wrote:
> This was a condition enforced in the first iteration of prompt sessions.
> It will be removed later, once the services support parallel processing
> of prompt requests.
We do this today. Which is, ironically, the only way it works as the
user can click the pay button again and we do a second prompt :-)
> The payments helper should be putting password prompts/etc as part of
> it's prompt providers, as far as I'm aware, there shouldn't need to be
> any app context switching when dealing with prompt sessions.
There would be if you had something like a password manager and you
needed to go look up the password and come back to the dialog. Or
perhaps for 2fa you'd go to authenticator.