Tels wrote:
although I am not sure why the "/P/" needs to be visible to the user (it is deterministic, after all), and it would be handy to have a "latest" revision URL. Which could be just: http://upload.wikimedia.org/wikipedia/en/Puppy.jpg and the software behind the back figures out what the exact latest revision is and under what /CapitcalLetter/ directory it falls.
Please read Brion's original message again.
These are things a human user shouldn't need to do or know about.
Serving static content usually amounts to just pushing bits, and that's all it should be. If you want it to be more than that, you need to call into a language that will supply an additional layer of logic before you can start pushing bits, which is usually enormously slower than being able to say "here's a link to a static file". You can serve the latter with all sorts of optimizations -- one example being in-kernel httpd, or one of the very fast userland ones.