Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 69939 invoked from network); 26 May 2004 07:55:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 26 May 2004 07:55:26 -0000 Received: (qmail 16625 invoked by uid 500); 26 May 2004 07:55:41 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 16595 invoked by uid 500); 26 May 2004 07:55:41 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 16554 invoked by uid 98); 26 May 2004 07:55:40 -0000 Received: from listx-apache@dstudio.clara.net by hermes.apache.org by uid 82 with qmail-scanner-1.20 (clamuko: 0.70. Clear:RC:0(195.92.195.171):. Processed in 0.016883 secs); 26 May 2004 07:55:40 -0000 X-Qmail-Scanner-Mail-From: listx-apache@dstudio.clara.net via hermes.apache.org X-Qmail-Scanner: 1.20 (Clear:RC:0(195.92.195.171):. Processed in 0.016883 secs) Received: from unknown (HELO cmailg1.svr.pol.co.uk) (195.92.195.171) by hermes.apache.org with SMTP; 26 May 2004 07:55:40 -0000 Received: from modem-2415.buffalo.dialup.pol.co.uk ([217.134.73.111] helo=sunbird) by cmailg1.svr.pol.co.uk with esmtp (Exim 4.14) id 1BStFM-0000Gb-ER for users@httpd.apache.org; Wed, 26 May 2004 08:54:44 +0100 From: "Rick" To: users@httpd.apache.org Date: Wed, 26 May 2004 08:53:37 +0100 MIME-Version: 1.0 Message-ID: <40B45B11.32348.12409FBF@localhost> Priority: normal In-reply-to: <40B192E5.9931.7624949@localhost> X-mailer: Pegasus Mail for Windows (v4.12a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Spam-Rating: hermes.apache.org 1.6.2 0/1000/N Subject: Re: [users@httpd] Conditional RewriteRule X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Thanks to everybody for all the help and suggestions, especially for: * reassurance that my original idea was basically OK-ish; * the regex (from Robert Andersson) to pad the filename; * hints (from several people) that maybe putting all our files into that hashed directory structure was not the best approach. As Nick Kew observed, this is a task for which there is more than one solution. Missing from my background info was the fact that our options are restricted -- the project is hosted on a shared hosting plan (there isn't enough money for anything better), so we can't choose our own filesystem, what we can do with Apache is limited to .htaccess, and we do have to be quite careful about our impact on the server. So I'm trying to think of the best solution available within this narrow framework. The first step is to ensure that our URLs are long-term independent of any plausible implementation -- which includes databasing (as suggested by Eugene Lee) as well as using static files. Right now I'm leaning towards databasing, which on a shared server is probably less robust, but URL rewriting should be simpler. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org