Hey Sanjiva: Sanjiva Weerawarana wrote:
I don't think we need to go that far .. that is, we've had this conversation before about making comments into actual resources (yes each one must have a URI but we're implementing them differently) and I'm not yet convinced we'd gain much by having them have a specific URI independent of the resource they comment against is useful or necessary.
Hm. Well, they MUST have a URI so that the remote stuff will work (i.e. referencing, editing or deleting, as per the protocol). If they're going to have a remote URI, that has to evince itself somehow in the API (whether surfacing all the way to the user or hiding somewhere). It seems to me returning the URI from addComment() is the right way to do that, so it can be used as a valid path to delete() at least. I'm certainly not saying Comments need to be versioned and taggable and all that, but they are "things with a URI", i.e. resources. I like that the same pattern would work with local or remote registries.
How would you suggest deleting a comment via the Java API?
/tag/foo and /tags is different - those are really queries.
I'm not sure what you mean here? --Glen _______________________________________________ Registry-dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/registry-dev
