For faster speeds, we suggest Ethernet. As part of the HTTP specification, the web server keeps track of who makes the request, thereby returning the response to the proper location. However, when a request is made of Helix via Osmosis, Helix itself must also keep track of this information. One such method is to use a unique identifier created as 'data' when a browser client accesses the Helix data base. A user name passed in by the browser client or an incrementing number created by Helix serves as possible unique values.
Subsequent submissions pass the unique value back to Helix and use it as a link for the session.
Osmosis uses the process name feature. When present, Osmosis puts the name into a local variable. If another variable exists with the same name, the script is queued, otherwise the script is run. Note that all four users all post the same field value to the Global Relation. We must wait for User 1's output before we can reuse the global value for User 2.