follow-up to dev call : ProfileInterceptorResult ?

[Tom Zeller]

> What I was suggesting is more like an interface with accessors for ID (the
> flow ID), creation time, expiration time, and probably methods to get the
> context and key (similar to what you're putting there).

At the moment, the flow descriptor has the functions/strategies for
looking up the storage context and key, for reads, so I was not
thinking the result class would have those methods.