Thanks for the guidance and pointers to existing issues. My project priorities are options for editing and paging, but I definitely agree those are peculiar enough to belong outside the Restlet core.
For now, I'm trying to extend via subclasses, even though that's a challenge given the existing code. For example, that private 'directoryContent' ReferenceList, built in the DirectoryResource constructor, makes alternate views aware of File properties (like size or modifiedDate) hard. I suppose my ideal would be a bare bones Diretory/files implementation in the core, refactored so an extension could get fancy in many ways. (The idea of boilerplate headers and footers comes from Apache configuration options which I believe date all the way back to NCSA HTTPd.) When you say parts of DirectoryResource are 'touchy', is that a technical or political warning? Would a patch splitting up some of its operations to separate overriddable methods, and/or moving some fields/methods from private to protected, be a worthwhile direction for me to try? - Gordon @ IA ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1105911
