+1, this looks really good to me;

One thing we imho should discuss is whether this should be using the api
package, like o.a.s.api.resource.collection; We could leave it in the
separate bundle as is right now, and once we consider it stable, move the
package to the official API package.

Carsten


2013/5/3 Amit.. Gupta. <amitg...@adobe.com>

> Hi Devs,
>
> Please vote for [0]. This is a proposal for Adding ResourceCollection to
> Sling. There is a patch [1] attached as well, as a first cut implementation.
>
> Summary:
> This proposal is to add a ResourceCollection interface and implementation
> that allows creation of collection of resources.
> Collection is a simple list of members, where each member contains path of
> resource it refers to. In future, we might need to store additional
> information with the member, hence following structure is proposed
>
> N: resourceCollection (nt:unstructured)
>         + P: sling:resourceType
>         + N : members (nt:unstructured)
>             + N: member_res1 > nt:unstructured
>                 + P: path > string, reference to actual resource
>             + N: member_res2 > nt:unstructured
>                 + P: path > string, reference to actual resource
>
> Your views on the same are requested.
>
> Thanks,
> Amit
>
> [0] https://issues.apache.org/jira/browse/SLING-2853
> [1]
> https://issues.apache.org/jira/secure/attachment/12581670/resourcecollection.zip
>
>


-- 
Carsten Ziegeler
cziege...@apache.org

Reply via email to