> Hi Deepal: > > Deepal Jayasinghe wrote: >> I went though the code and looked what actually I have done then I found >> that the only problems in the resource operations like raring and >> tagging. Adding , delete and accessing resources does not have any >> issues, and it has follow the API in the wiki correctly [1] . Now I > > It does????? Then why, as I mentioned before, are we doing a POST to > a non-existent URL to create a new resource? > > If I want to create /d1/d2 in a blank new registry, the protocol > should be to submit two collection-creation requests as follows: > > POST / > Slug: d1 > <representation of directory> > > 201 Created > Location: http://localhost:8080/wso2registry/atom/d1 > > POST /d1 > Slug: d2 > <representation of directory> > > 201 Created > Location: http://localhost:8080/wso2registry/atom/d1/d2 Why cant we do this in one step , even registry support , creating a set of directory at once. > > (actually we need to do a HEAD at each step too to make sure there > isn't already something there... and cache the structure locally so > we don't have to do that every time) Yes I agree.
_______________________________________________ Registry-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
