Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Timestamp integration to API #120

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments
Closed

Timestamp integration to API #120

openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments

Comments

@openstreetmap-trac
Copy link

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.

@openstreetmap-trac
Copy link
Author

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).

Imi.

@openstreetmap-trac
Copy link
Author

Author: immanuel.scholz[at]gmx.de
[Added to the original trac issue at 1.00pm, Wednesday, 5th April 2006]

DELETE requests do not specify the timestamp yet.

Maybe &timestamp=xxx in the url?

@openstreetmap-trac
Copy link
Author

Author: grand.edgemaster[at]gmail.com
[Added to the original trac issue at 4.22pm, Wednesday, 6th May 2009]

Issue fixed by version requirement in 0.6

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant