-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memento protocol #133
Comments
Yeah, that would be a good idea, thanks! I've looked into Memento a bit, and the first big blocker is that it represents time using a computer's local time. Unfortunately, that doesn't work for synchronization over a distributed network, because time becomes relative, and you can't rely on clocks. Instead, you need to construct a partial order of events. I other words, Memento models time like:
But for distributed sync, we need something like:
In the long run, though, we'd like to be able to support all the features we need for versioning and time in HTTP. For instance, we want to support local times as time identifiers too, so this works in Braid:
There might be useful features in Memento for history representations that we don't have in Braid, and should consider merging in. What do you think? |
^ Updated my comment above |
@toomim I do understand the difference in perspective. Before I share some ideas re how Memento could still be used in relation to braid, I have a question: While version identifiers are crucial in braid, is it safe to assume that the datetimes of these versions are available too? |
I had a look at the HTTP Resource Versioning I-D and was wondering whether the combination of two existing headers - To request a version, the combination of the existing An interesting result of this approach would be the ability to issue requests with only
I see no alternative in existing approaches to the proposed As a side note regarding the proposed |
To your old question:
I don't think this is safe to assume. I'm aware of at least a few collaborative text editors that don't store datetime timestamps for the edits. As for your idea of combining The issue with
Yeah, this is a common feeling, but I haven't seen a good reason for it, and it sure seems a lot simpler and more sensible to use the same header. I'd love to hear a good reason for it. One issue with |
When it comes to resource versioning, it seems appropriate that braid would reference RFC7089: HTTP Framework for Time-Based Access to Resource States -- Memento.
The text was updated successfully, but these errors were encountered: