I'm interested in enhancing the Directory restlet. For example (though I may not get to all of these):
- displaying size and modification-time in listings - allowing a customizable header/footer in listings - supporting paging through certain file types (probably through query-string parameters that cause a non-default representation) - supporting editing of certain file types (most simply, via a textarea full-file editor) Some aspects of the current code flow are daunting. (In particular, delegation to the Engine to create a DirectoryResource, and long twisty methods like DirectoryResource's constructor.) Any tips? Would it break any core assumptions for my Directory subclass to instantiate a DirectoryResource itself, skipping the detour through Engine.createDirectoryResource()? Would refactorings of Directory or DirectoryResource be welcome in the core project? Thanks for any guidance, - Gordon @ IA ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1067321
