Devise a method for the easy resetting of a resource.

[GoogleCodeExporter]

When diffs become too large or a resource's contents are changed entirely, 
there needs to be a sane system for rebasing the resource and starting over in 
the generation of the deltas.  Currently, the only way to start over with a 
resource is to rename it or delete the corresponding resource store folder.  

Although this second method is not too bad, it's not easy to identify which 
resource store folder corresponds to which resource.  If nothing else, an 
artifact holding these mappings should be generated so that the correct folder 
can be quickly identified for deletion.

Should there be some sort of administrative servlet for this and other resource 
management tasks?

Original issue reported on code.google.com by joshharr...@google.com on 17 Aug 2010 at 4:44

[GoogleCodeExporter]

We should put in place a method which will start over the generation of delta 
when this delta is becoming too large.

To determine if we need to start over the generation of delta, we could use an 
automatic process, which will be based on something like :
(Max diff file size for a resource) > (first file version / X)
where X should be determined. This will be the fun part :)
The X variable could also be configurable by the user.

It's a good idea to use a specific adminstrative servlet to force the process 
if needed.

Original comment by ichae...@gmail.com on 17 Aug 2010 at 7:48

[GoogleCodeExporter]

About the administrative features, a better way would be to use a JMX MBean to 
handle the adminstrative operation instead of a servlet.

Original comment by ichae...@gmail.com on 5 Sep 2010 at 3:02

[GoogleCodeExporter]

Original comment by joshharr...@google.com on 16 Dec 2010 at 5:44

• Added labels: Performance