This may be silly but any way to clean up the ucl so the big ugliness, like
.../swf-phonebook/phonebook.htm;jsessionid=8FBC0032F6FC1272E8BBCE0BD 6992799?_flowExecutionKey=_c5FE0D65E-7F80-29CB-5F58-195B282C7651_kFCBE47A5-D88B-4997-E5BC-D17D6E48FC98
does not show up. This kind of thing will get dropped completely from google and co.
Just plug in a custom FlowExecutorArgumentHandler at the level of the FlowController. Possibly combine this with custom id generation to get the lengthy UUIDs out of the way. All of this is pluggable so should be relatively easy to do.
Erwin
Well, minus the session id that got put in there, that's a flow execution ucl--pointing to a temporal resource -- a flow execution -- not a durable resource.
The actual flow definition resource ucl like app/search-flow is clean and indexable and durably stable -- however specific flow execution instances are not - as they manage the local state of an ongoing user interaction.
As Erwin mentioned, you can control the ucls to some degree as well as the keys that get generated, but fundamentally you need to understand the difference between a flow definition resource and a flow execution resource. One is single and static, another is temporal associated with a given user interaction / user session.
Keith |
Post at 2011-4-15 15:44
| This Author's Posts Only
