ProfileRequestContext accessibility outside flow actions

[Cantor, Scott]

On 8/13/15, 3:47 PM, "dev on behalf of Marvin Addison" <dev-bounces at shibboleth.net on behalf of marvin.addison at gmail.com> wrote:


>
>You're right -- that would be true in general. I wasn't thinking about a flow that paused while rendering a view state. On re-reading your initial response, I see you said as much but I didn't pick up on it. What I suggested will work for my case since
> the entire flow runs in single request/response transaction via X509Internal.

Even there, that only works until we wire in the local storage support (though I know in your case you wouldn't be using it, but you see my point). For those using it, it will have to render a view or two most of the time to pick up and save off the storage. That's why I've been really anti- the use of things like query string communication and such within the flows.

>Agree it seems innocuous, and I would argue it's generally beneficial. Surely the need to get at context tree data from outside the flow execution context will arise again. Are you open to a Jira enhancement request?

We should collectively think about it before we do it for real, but that's fine.

-- Scott