As I've been working on the implementation of the API I've come across a few things that should probably change. I wanted to outline them here for discussion before making the changes.
The Collection interface should have setResourceType and getResouceType methods. These had been piggybacked on set/getProperty but this is important enough functionality that it should probably be a regular method. The Resource interface should have a getResourceType method so that you can know what kind of resource it encapsulates. In Collection there should probably be a getChildCollection method to retrieve a collection relative to the current collection. In Collection there is currently a getChildCollections method that returns a list of Collection instances. This would probably be better as a listChildCollections method that returns a list of child collection names instead of actual collection instances. You could then use getChildCollection to retrieve the Collection instances as needed. In Collection there should probably be a way to test for the existance of a Resource prior to retrieving/changing/deleting it. In Collection there should probably be a way to test for the existence of a particular service. I think that's it for now. -- Kimbro Staken Chief Technology Officer dbXML Group L.L.C http://www.dbxmlgroup.com ---------------------------------------------------------------------- Post a message: mailto:[EMAIL PROTECTED] Unsubscribe: mailto:[EMAIL PROTECTED] Contact adminstrator: mailto:[EMAIL PROTECTED] Read archived messages: http://archive.xmldb.org/ ----------------------------------------------------------------------
