[Registry-dev] APP

[Glen Daniels]

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

(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)

This is not what we're doing now, is it?  I doubt this is the only place 
that's divergent from the protocol design.

> started to change the implementation to cope with the API in the wiki ,
> but I have a number of area which I have doubt and need to clear them
> before I continue.
> 
> - How to get logs
>    should that be /[r1];logs

/[r1];log

> - Get versions
>    /[r1];versions , then the text of the feed will be the versions for
> the given resource.

+1

> - /[r1];tags:[tag+username]  , I can not understand the use of this

There was some debate about this.  IIRC some folks thought this might be 
useful for deleting a particular tag by a particular user.  Others 
thought it wasn't needed at all.  I'm in the latter camp.

After this, we had a discussion on the list about deleting tags where we 
decided that if someone who wasn't the owner of a resource deleted a 
tag, they would only delete their own "tagging", and if the owner of the 
resource deleted a tag it would delete ALL "taggings" (completely clear 
the tag from the resource).  I believe that discussion might have 
obviated the need for this - Jonathan, you were the one who wanted this 
URL, right?  What do you think?

> -For the rating and tagging what should be the structure of the entry

I don't think there should be entries at all for ratings/tags, personally.

> - Did we finalized on ";" as the parameter separator.

For now, yes.  If we need to change it for some reason we can do so later.

Thanks,
--Glen