Stream: implementers
Topic: ReadHistory vs Interaction.VRead in CapabilityStatement
Gabriel (Nov 30 2017 at 23:53):
Is there any guidance on the difference between turning on and off ReadHistory and adding the VRead interaction?
I am not completely sure about the meaning of these combinations:
ReadHistory=True + VRead exists = Type/_history is supported and you can query any version
ReadHistory=True + No VRead
ReadHistory=False + VRead exists
ReadHistory=False + No VRead = I am assuming this means the service has no Type/_history support
Any idea what is the right expected behavior for the 4 combinations?
Grahame Grieve (Dec 01 2017 at 00:10):
it doesn't really make sense to say readhistory=true when there's no vread
Gabriel (Dec 01 2017 at 01:09):
Thank you @Grahame Grieve , a follow up to that would be, what happens when you have readhistory=false with the rest of the interactions related to versioning?
If we have readHistory=false and vread present
- Can we do a GET on type/_history/{versionid} where {versionid} is the latest version id of the object. If this is not allowed either, then what happens with the location header after a create is done? Does the version id get trimmed from the url to the resource?
How does setting readHistory=false affect history-instance and history-type? Is the whole endpoint disabled?
Grahame Grieve (Dec 01 2017 at 01:14):
well, if you have vread not readHistory, you support vread of the current version, but not past versions. I don't know what it means to claim you support history and not hve readhistory = true
Last updated: Apr 12 2022 at 19:14 UTC
