sql server - Azure Mobile Service concurrency handling in SQL? -


i implementing azure mobile service , have set of objects can accessed multiple users, potentially @ same time. problem can't find lot of information on how handle potential concurrency issues might result this.

i know "azure tables" implements e-tag check. there out-of-the-box solution azure mobile services 1 sql ? if not, approach should going here.

should implement e-tag check hand? include guid of object generated every time object saved , checked when saving. should relatively safe way it?

for conflicts between multiple clients, need add detection/resolution mechanism. use "timestamp" (typically sequentially incremented version number) in table schema , check in update script. fail update if timestamp used client reading older current timestamp.

if want use etags via http headers, use custom apis. looking enabling crud scripts set headers not available today. separately, looking offline scenarios well.

(prog manager, windows azure mobile services)


Comments

Popular posts from this blog

c++ - Creating new partition disk winapi -

Android Prevent Bluetooth Pairing Dialog -

VBA function to include CDATA -