search

xregistry / spec

xRegistry related specifications
https://xRegistry.io
Apache License 2.0
35 stars 6 forks source link

Should epoch/modifiedat be changed when no properties are updated? #114

Closed duglin closed 5 months ago

duglin commented 5 months ago

when a PUT/POST/PATCH is done such that the entity doesn't have any properties updated (e.g. PUT .../GROUPs/gID. + {}), should the epoch and modifiedat properties be updated?

Proposal: yes for two reasons. 1) I think having consistent processing (ie. do a loop over all incoming props, and the when done update the epoch/modifiedat) is good - even if the loop exits immediately, 2) I think having a "touch"-like feature could be handy

I think we need to be explicit whatever way we decide so that we have interop (we're consistent) on whether a client's cache of an entity (based on epoch) will become stale or not based on this empty update operation.

duglin commented 5 months ago

Agreed on the 5/17 call

duglin commented 5 months ago

fixed by #124