[ 
https://issues.apache.org/jira/browse/JSPWIKI-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588270#action_12588270
 ] 

Florian Holeczek commented on JSPWIKI-110:
------------------------------------------

{quote}
I wonder could this be solved by having a /wiki:timemachine/ -path in the repo, 
then put in a Node for each date, and put in a lot of properties with UUID 
links to the particular pages/version instances.
{quote}
I wonder if I understood this right... doesn't this imply creating such an node 
each time _any_ page is changed, while this node contains uuids of all valid 
page versions as of timestamp x?
If so, you'll run into severe performance problems.

{quote}
Or, you could somehow use a separate workspace for each date - workspaces can 
share Nodes in different paths as long as the UUID is the same.
{quote}
That would be even worse!? Creating a new workspace every time a page is 
changed?

I think saving any states is the wrong way here. The operation is too expensive 
and infrequently needed.
It's a bit comparable to creating indices in databases: Sure you can create an 
index for anything that's ever searched for, but this makes inserts and updates 
very slow, since not only the data itself, but also the indices have to be 
updated.
This is why I think this should be part of the application logic, which has to 
search the repository on demand. What has to be modeled in the repository is 
that deleted pages aren't removed upon deletion.

> time machine
> ------------
>
>                 Key: JSPWIKI-110
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-110
>             Project: JSPWiki
>          Issue Type: Improvement
>         Environment: n/a
>            Reporter: Florian Holeczek
>            Priority: Minor
>
> Versioning and viewing the history is limited to one single page. If you want 
> to see the whole wiki state as of timestamp X, you have to manually open the 
> corresponding history entry of each page. Therefore, a time machine may be an 
> interesting feature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to