[Registry-dev] Resource delete and version handling

[Paul Fremantle]

Deepal

Let's suppose we have a resource

/foo/r1 [version 1]

We delete that
I'm assuming that a deletion is simply a new version with some kind of a 
marker saying this resource is deleted.
So we get

/foo/r1 (deleted) [version 2]

Now I add
/foo/r1

So this becomes version 3.

By the way this is exactly what happens with the Apache wiki site 
(MoinMoin).

I think this is a good approach and will certainly be understandable to 
users. I know SVN does this differently, but in this case I prefer this 
model.

Paul

Deepal Jayasinghe wrote:
> I am in the process of handling resource delete and I have faced a
> problem of handling the history for the deleted resources. Say we have a
> resource called "foo/r1" and we delete that. And later we add a resource
> with the same path then what should be the procedure ?
> 
> Are we going to delete the history for the previous resource ? or we are
> not going to allow to add a resource with the same name once we delete
> the resource.
> 
> This problem is due to the fact that we keep path as the key for
> identifying the resource not the resource ID. If we can keep ID as the
> unique identifier then we can solve the problem. Then we can burn the ID
> into the UI and send that as the query parameter when someone click on a
> resource as below,
> 
> localhost:8080/wso2registry/foo/r1?id=100
> 
> Thanks
> Deepal
> 
> 
> _______________________________________________
> Registry-dev mailing list
> Registry-dev at wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
> 

-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair

Office: +1 646 290 8050
Cell: +44 798 447 4618

blog: http://pzf.fremantle.org
paul at wso2.com

"Oxygenating the Web Service Platform", www.wso2.com