You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: andy_j_robinson[at]blueyonder.co.uk [Submitted to the original trac issue database at 2.33pm, Friday, 30th December 2005]
Add a timestamp to the data returned from the server so that java console logs can be better used for server performance monitoring against user activity.
The text was updated successfully, but these errors were encountered:
Author: immanuel.scholz[at]gmx.de [Added to the original trac issue at 2.36pm, Wednesday, 15th February 2006]
I would ask to have a timestamp on every object returned, stating the last modified time. This allows later (when uploading) the server to do proper versioning control:
If a client tries to overwrite an outdated object, the server can refuse that. This is only possible if the client can provide the "version" he thinks is currently the latest. A timestamp is the easiest way of "version" specifier (and usefull for other things too).
Reporter: andy_j_robinson[at]blueyonder.co.uk
[Submitted to the original trac issue database at 2.33pm, Friday, 30th December 2005]
Add a timestamp to the data returned from the server so that java console logs can be better used for server performance monitoring against user activity.
The text was updated successfully, but these errors were encountered: