> Why would you run a second path?
Ah, yes, of course. It had become so ingrained in me not to use my app layer to serve static files I didn't even consider that -- I was thinking, boy, routing from lighttpd -> perlbal -> web app --> mogilefsd and back again doesn't make any sense! What about caching? In the excellent thread about serving best practices, there were a number of places for memcached to be plugged in -- obviously it'd be pretty easy to have the app store the key/path(s) in memcached, but * I'm guessing you'd need to store all the possible paths in memcached, in case one of them is invalid so perlbal can go down the list? * Are there other places where perlbal can link directly to memcached (without going through the app layer)? <http://www.fluther.com>
