On Fri, Apr 24, 2009 at 3:03 PM, Vidar Ramdal <[email protected]> wrote: > For a start, the bundle could contain this: > > - Script/servlet for retrieving a tag's meta-info (/tags/tagname) > (at least as an example - users would want to create their own script) > > - Script/servlet for retrieving content tagged with a certain tag > (/tags/tagname.list) > (same as above) > > - Script/servlet for deleting a tag > When a tag is deleted, it should be removed from all nodes that uses it > > - PostProcessor for adding tags > This could work like this: The postprocessor monitors POSTs, and > checks if a "tags" property is modified. If the "tags" property > contains a new tag (a tag that does not yet exist under /tags), it is > created there.
You can also do this as a JCR observation listener. This will then ensure consistency of the tags property for JCR API clients as well, not only Sling HTTP clients. You have to think about duplicates and deleted tags as well. Regarding creation: it is also necessary to check write permissions before creating a tag, this might require two requests for a smooth user interface (no exceptions on write). This is the drawback of the implicit relation between content and the tag tree. Regards, Alex -- Alexander Klimetschek [email protected]
