There needs to be an indicator that a character sheet has been updated. Consider having a "version number" on associated with the base character sheet record: user loads the sheet, it's @r1; the DM loads the sheet, also @r1; DM updates values on the sheet, now it is @r2; user is notified of the change, automatically updates. Consider using a Unix timestamp that has milliseconds.
This functionality is useful for keeping the page up-to-date. It can be checked for conflicts when submitting updates and can then block conflicting changes. Using Ajax + long polling (i.e. Comet programming), changes can be displayed immediately without blocking... though modifications made to a value the user is changing would have to be handled elegantly.
There needs to be an indicator that a character sheet has been updated. Consider having a "version number" on associated with the base character sheet record: user loads the sheet, it's @r1; the DM loads the sheet, also @r1; DM updates values on the sheet, now it is @r2; user is notified of the change, automatically updates. Consider using a Unix timestamp that has milliseconds.
This functionality is useful for keeping the page up-to-date. It can be checked for conflicts when submitting updates and can then block conflicting changes. Using Ajax + long polling (i.e. Comet programming), changes can be displayed immediately without blocking... though modifications made to a value the user is changing would have to be handled elegantly.