> > A cool side effect of this will be that listResources() in Collection > > will then probably return a ResourceSet, too, so I will have a > > ResourceIterator there. > > I still think listResources should return an array of strings. There are a > lot of times where you just need a list of IDs and not all the actual > resources. An example is any kind of content browser. Using a ResourceSet > would be very inefficient. Overall, it seems to me that wanting to > retrieve all resources in the collection will be a pretty rare operation > and is covered well enough with listResources. What are the solid use > cases that would justify adding a new ResourceSet getResources() method in > addition to listResources?
You're right, of course. Forget it. That was because I was coding a lot of tests recently where I need a deleteAll(), so an Iterator returning Resources would have been cool. Jeremias Märki mailto:[EMAIL PROTECTED] OUTLINE AG Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern Fon +41 (41) 317 2020 - Fax +41 (41) 317 2029 Internet http://www.outline.ch ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact administrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
