René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Allow persistence of Op history","articleBody":"To ease reproducibility, `OpHistoryService`s should be able to persist their histories, and from that persisted data be able to restore that history into a readable form. \r\n\r\nIdeally, this would be accomplished using some `OpHistoryService` API along the lines of:\r\n```java\r\npublic void recordHistory(URI outputLocation);\r\n\r\npublic void restoreHistory(URI inputLocation);\r\n```\r\n(One) implementation of these methods might benefit from `scijava-persist`\r\n\r\nThe restoration of a history would ideally be possible independent of original `OpHistoryService` implementation (i.e. a `FooOpHistoryService` should be able to restore a `BarOpHistoryService`), but this might be too strict an approach. Potential problems may include:\r\n* Situations where aa `BarOpHistoryService` doesn't have all of the Ops listed in the history created by the `FooOpHistoryService` that recorded the history\r\n* Limitations on extensibility (all `OpHistoryService`s would have to serialize/deserialize in the same way, or at least know how to deserialize numerous types of serialized histories)\r\n\r\nOne interesting thought: upon a call to `restoreHistory`, should the `OpHistoryService`:\r\n* Erase/Record any previously logged history?\r\n* Meld its previously recorded history with the history recorded at `inputLocation`?","author":{"url":"https://github.com/gselzer","@type":"Person","name":"gselzer"},"datePublished":"2021-07-14T21:03:31.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/66/scijava/issues/66"}