execution vs flowExecutionKey? whose, link

amy

When specifying the flow ID in a link, I create it like this:Code:
lt;a hrcf=”${flowExecutionucl}amp;_eventId=someStateHere”gt;Do Somethinglt;/agt;
Resolved as:       Code:
lt;a hrcf=”/someApplicationContext/someFlowId?execution=e1s4amp;_eventId=someStateHere”gt;Do Somethinglt;/agt;
When the view is rendered, the flowExecutionucl includes the context relative URI for the current flow execution in addition to a request parameter quot;executionquot; (whose value indicates the current execution and step).

When specifying the event ID using a form, I also need to include a variable called quot;_flowExecutionKeyquot; who''s value is stored in a variable which Web Flow provides called quot;flowExectionKeyquot;  For example:Code:
lt;input type=”hidden” name=”_flowExecutionKey” value=”${flowExecutionKey}”/gt;
Is resolved as:Code:
lt;input type=”hidden” name=”_flowExecutionKey” value=”e1s4”/gt;
What is the difference between quot;executionquot; and quot;flowExectionKeyquot;?  The variable quot;flowExectionKeyquot; is provided in the view, but quot;executionquot; is not.  They seem to be doing the very same thing.  If they are not different, what drove the two different naming conventions?