In Instrumenting co-operating app I showed how a web app might create some data in a dead drop to pass back to VBA. In my example, there are many worksheets, each of which may have outstanding messages, so I need a way to track responses I might be expecting from particular deadDrop keys. I've created a log that gets automatically updated each time a web app is generated with its deadDrop key. From time to time I can run a process that examines all the outstanding message keys and checks for messages. You don't need to do this of course - it's just an easy way to handle backlogs of requests and storing their keys
This a one liner
to get a sheet that looks like this
Here I create a deaddrop handle and update the log with the new outstanding request. The expectation is that whoever called this will pass the generated key on to the co-operating app.
My example is fairly lengthy, but the process is straightforward. Check the log for unprocessed entries, get the data if any, update the log entry, delete the message
Services > Desktop Liberation - the definitive resource for Google Apps Script and Microsoft Office automation > Things that have been deprecated > Google Apps ScriptDB > ScriptDB as a dead drop >