title: Am I using the Google Apps Script Lock Service correctly?
body: <p>I have 3 Apps Script functions in a script. The script is deployed as a public access Web App.</p>
  
  <p>Each function reads from a it's own google sheet.  Each function does not write anything to the sheets.</p>
  
  <p>I have applied the Apps Script 'LockService' to each function to prevent multiple users accessing the spreadsheets, via the webapp, at the same time. In effect making each user wait until the previous user's script has finished reading.  They they get to read the 3 sheets.</p>
  
  <p>I've found this can sometimes create a bit of a delay of 4 or 5 seconds for users before the App is updated - which is quite off putting.</p>
  
  <p>My question then is should I -
  a) bother with the LockService, as I am just reading the spreadsheet data and perhaps the main purpose of LockService is to prevent conflicts between concurrent read AND writes</p>
  
  <p>Or </p>
  
  <p>b) am I correct to implement it, as reading data concurrently could also cause conflicts is getting things like Range values etc.</p>
  
  <p>thanks</p>
  
  <p>EDIT:  if option 'a' then I wonder what the purpose of LockService is? Is one reason perhaps (as I have elsewhere in other scripts) when you use multiple 'google.script.run.'  One after the other to access the same spreadsheet, via different functions, then -  as these run asynchronously - there could be conflicts created if both requests are trying to Get data.</p>
  
  <p>just musing really....</p>