Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 61824 invoked from network); 11 Nov 2004 13:50:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 11 Nov 2004 13:50:32 -0000 Received: (qmail 62866 invoked by uid 500); 11 Nov 2004 13:50:30 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 62810 invoked by uid 500); 11 Nov 2004 13:50:29 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 62773 invoked by uid 99); 11 Nov 2004 13:50:29 -0000 Received-SPF: pass (hermes.apache.org: local policy) Received: from [212.227.126.187] (HELO moutng.kundenserver.de) (212.227.126.187) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 11 Nov 2004 05:50:29 -0800 Received: from [212.227.126.207] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1CSFLF-0007xS-00 for dev@forrest.apache.org; Thu, 11 Nov 2004 14:50:25 +0100 Received: from a81-14-145-179.net-htp.de ([81.14.145.179] helo=localhost) by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1) id 1CSFLE-0001oA-01 for dev@forrest.apache.org; Thu, 11 Nov 2004 14:50:25 +0100 Date: Thu, 11 Nov 2004 14:48:48 +0100 From: Ferdinand Soethe X-Priority: 3 (Normal) Message-ID: <1839141925.20041111144848@soethe.net> To: dev@forrest.apache.org Subject: Question about directory structure MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:f75f2bd431147ec08213cc5cdb6cedb7 X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I find it quite awkward to have a directory structure where additional files for my XML-Pages are in a similar structure _that is one level down_ from the XML-directories. Current situation: +---Berufliches +---BookCrossing +---Forrest +---HospitalityClub +---images +---Kajak � +---Boote � +---Tourenberichte +---xdocs +---Berufliches +---BookCrossing +---Forrest +---HospitalityClub +---images +---Kajak +---Boote +---Tourenberichte I wonder what the reasoning behind this is and wether I'm the only one who'd find a structure where there are _two branches on the same level_ to be more intuitive and less error-prone. Alternative approach: +---files +---Berufliches +---BookCrossing +---Forrest +---HospitalityClub +---images +---Kajak +---Boote +---Tourenberichte +---xdocs +---Berufliches +---BookCrossing +---Forrest +---HospitalityClub +---images +---Kajak +---Boote +---Tourenberichte -- Thanks for your feedback, Ferdinand Soethe