Comments below
2009/6/8 Mike Wilson
<mikewse@...>
Mike Wilson wrote:
3) Invocation id
...
The invocationId needs to uniquely identify each
call to the server and basing off the scriptSessionId we would just have to
add a sequential call index number that we can keep locally in the client
layer.
I should mention that we already have this
sequential number as well; the batch id. So, the combination of scriptSessionId
and batchId uniquely identifies every call to the server, including file
uploads.
My original invocationId used scriptSessionId + batchId but I moved to a random number to support a DWR mode without script sessions. Perhaps I could check if scriptSessionId is null and only use the random number in this case.