follow-up to dev call : ProfileInterceptorResult ?

[Tom Zeller]

> Again, in your example case, maybe the flow reads from a specific key
> derived from the profile context using a function defined inside the flow,
> and then a wildcard as a fallback, so there's no single answer to what the
> key is. But a given object produced by the flow could carry along the
> knowledge of what to write back to in a method or a pluggable function
> inside it.

Okay. So, the flow descriptor has the "lookup" context and key(s). The
result object has the pluggable "write" context and key.

Do you think the interceptor context should hold a single result or a
collection of results ? It doesn't really matter to the write action,
but I'm wondering if there is a use case for multiple results returned
from the flow.

> Basically, I think reading data is probably flow-specific in some cases.

Makes sense.