2009/4/23 Vidar Ramdal <[email protected]>: > These are just some loose thoughts that have been brewing in my mind > lately, after reading Richardson/Ruby: RESTful Web Services [1]. > > In order to make Sling (even) more buzzword compliant, I have been > thinking about a system for tags.
> 2009/4/24 Juan José Vázquez Delgado <[email protected]>: >> ...That is a nice feature but IMHO is more suitable for specific use >> cases, such as CMS systems, than for Sling itself.... 2009/4/24 Bertrand Delacretaz <[email protected]>: > IMHO that shouldn't prevent implementing it under contrib - not all > Sling users will need it, but using Sling for CMSish apps is certainly > a common use case. Certainly, this could be a bundle supplied under contrib. 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. Does this sound as a reasonable approach? -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Akersgata 16, N-0158 Oslo, Norway +47 21 531941, ext 2070
