First off, way to not use a paste site. :-) Second, no, they're not heirarchical, you're just used to them being that way. They're data structures, which are

First off, way to not use a paste site. :-) Second, no, they're not heirarchical, you're just used to them being that way. They're data structures, which are organized however I like them. In nginx they're hierarchical, in Mongrel2 they'll mostly be relational. Third, like I said before, the advantage is tooling. Managing the Mongrel2 configs from other languages, scripts, shells, and remotely with automation will be much easier than what you have in an nginx config. But, here's a thought: What if you could feed an nginx config to a tool and it spit out the Mongrel2 config to replicate it? Wouldn't that be slick?