On Fri, Oct 3, 2008 at 4:23 PM, 80n <[EMAIL PROTECTED]> wrote: > On Fri, Oct 3, 2008 at 3:54 PM, Frederik Ramm <[EMAIL PROTECTED]> wrote: >> Shaun McDonald wrote: >> > Should changesets automatically be closed after a period of time? If so >> > how long? > > Why does a changeset need to even have an open/closed state? Its just a > unique identifier for a set of changes.
and a more efficient way of storing user info and created_by tags ;-) >> > Are changesets useful if they are never closed, or empty? >> >> With that logic, a never-closed changeset would not happen (unless >> someone tries really hard!). An empty changeset is useless I believe. i can see several cases where open-ended changesets would be useful. e.g: if i have a lot of tracks/pictures it may take several days to input and upload, but they're still part of the same logical set. also, we might like to use changesets for categorisation of edits, like flickr tags. since changesets are not atomic, nor can they be automatically reverted, is it useful to be able to close changesets? >> > Should there be a way for an application to be able to query and check >> > to see if it has an open changeset to use, thus preventing open >> > changesets? >> >> It would be good style for an application to remember any changesets it >> has opened and try to re-use them; however if it crashes and loses track >> of a changeset that would not hurt since the changeset would >> automatically "expire". >> >> Bye >> Frederik >> >> -- >> Frederik Ramm ## eMail [EMAIL PROTECTED] ## N49°00'09" E008°23'33" >> >> _______________________________________________ >> dev mailing list >> dev@openstreetmap.org >> http://lists.openstreetmap.org/listinfo/dev > > > _______________________________________________ > dev mailing list > dev@openstreetmap.org > http://lists.openstreetmap.org/listinfo/dev > > _______________________________________________ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
