Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.
This project is archived and is in readonly mode.
Rails is going to the trouble now of publishing etags but they are not being used by ActiveResource's PUT to prevent lost updates.
For example,
client A GETs Resource X (etag 1)
client B GETs Resource X (etag 1)
client A PUTs Resource X (new etag 2)
client B PUTs Resource X (new etag 3)
client B has overwritten A's changes silently
ActiveResource should be sending If-Match: "etag" which should fail with 412 if the etag has already changed.
etags are also useful with DELETE and GET in the case of #reload()
Reported by Tim Olsen · July 18th, 2008 @ 10:50 PM
Staling out, please reopen if this is still a problem.
October 28th, 2008 @ 04:27 PM
