[27862] in North American Network Operators' Group
non-op
daemon@ATHENA.MIT.EDU (James Paul)
Mon Mar 20 19:33:56 2000
Date: 20 Mar 2000 16:29:44 -0800
Message-ID: <20000321002944.19497.cpmta@c004.sfo.cp.net>
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: nanog@merit.edu
From: James Paul <jamespaul@metconnect.com>
Errors-To: owner-nanog-outgoing@merit.edu
I apologize if this is off topoic…
I am researching the deployment of a free personal web-hosting service. Normally each user's html documents reside in a subdirectory of the document tree where the subdirectory is named for the user.
…/htdocs/
/ \
/ \
user1 … userN
Thus a users URL is www.site.com/userN.
We currently have about 5000 users on the service. This is spread across three different single directory filesystems. As the number of users grows I imagine that this will become unworkable due to the nature of the file systems. One solution is to put groups of users in several subdirectories but this could make the user URLs messy.
www.site.com/sub1/sub2/userN
Can someone please comment on methods of keeping short clean user URLs while making the storage of many small web-pages more efficient and scaleable? What kind of backends are currently being used to serve up plain old static content with inline stuff? Also, how are directories being indexed for retrieval?
How have are the larger installations currently working this?
Thanks in advance,
James Paul
