On Jan 5, 2010, at 7:08 PM, Chris Robertson wrote: > If the requests made to the parents has been normalized by the url_rewrite_program, then you shouldn't need a storeurl_rewrite_program at all. I'm thinking about YouTube and other CDN content, where I can't rewrite the request (since that would make the URL invalid), but I want to map URLs to a single canonical instance. My theory is that since this happens just before the content hits the store, it will need to happen independently on each backend. However, I wasn't quite sure how this would interact with peering (will the frontend ask the peers for the real URL, or the storeurl_rewritten version)? >> - I'm using round-robin for the backend peer selection. Should I switch to carp, or is that overkill when the instances are on the same physical box? What advantages does carp have? > > CARP routes a given request to the same parent every time. Since cache can't be shared between instances (on the same server or not) this can aid caching efficiency. Sounds like an excellent reason to me. =) I'll definitely make that change, then. Thanks, Jason -- Jason Healy | jhealy@xxxxxxxx | http://www.logn.net/
