Remix's concurrent submissions are fundamentally flawed (without causal ordering) | Lobsters

13

Remix's concurrent submissions are fundamentally flawed (without causal ordering) distributed dashbit.co
via amw-zero 6 months ago | caches
Archive.org Archive.today Ghostarchive
| 3 comments

3

1. 2
  
  easrng 6 months ago
  
  what if the server returned a timestamp for when the db read completed so the client could ignore responses if they already had a fresher version?
  1. 2
    
    amw-zero 6 months ago
    
    You should write a TLA+ model or something and see if it affects correctness.
    1. 1
      
      easrng 6 months ago
      
      sorry I don’t speak formal methods 💔

🇬🇧 The UK geoblock is lifted, hopefully permanently.