On Thu, Jun 18, 2009 at 09:23:10AM -0000, Andrew Bennetts wrote:
> Julian Edwards wrote:
> [...]
> > collision and re-load the form with the current data. If you want to be
> > fancy, you can do a hash per-field to be able to show which fields
> > collided.
>
> Really fancy would be including a hidden timestamp field, and then if the last
> update is newer than that use the BugActivity table to figure out what changed
> since the user loaded the page...
Since we now track the changes to the bug a lot we could actually do
that... Unfortunately the changelog isn't structured enough to be
reliable enough for collision detection (well, maybe, but probably not).
The hidden fields thing is probably the easiest way to do this, though
it feels kinda hackish.
On Thu, Jun 18, 2009 at 09:23:10AM -0000, Andrew Bennetts wrote:
> Julian Edwards wrote:
> [...]
> > collision and re-load the form with the current data. If you want to be
> > fancy, you can do a hash per-field to be able to show which fields
> > collided.
>
> Really fancy would be including a hidden timestamp field, and then if the last
> update is newer than that use the BugActivity table to figure out what changed
> since the user loaded the page...
Since we now track the changes to the bug a lot we could actually do
that... Unfortunately the changelog isn't structured enough to be
reliable enough for collision detection (well, maybe, but probably not).
The hidden fields thing is probably the easiest way to do this, though
it feels kinda hackish.
status triaged
importance medium