Gunnar Wolf escribió: [snip] > > So, people: What do you think? I want three basic things: > > 1- Human readable/editable. And no, I don't see either XML or > a!long!string!of!elements followed by > a!long!string!of!repeated!elements implementing a perverted kind of > nesting as human-editable - It would surely lead to pain! > > 2- The ability to have comments. Yes, probably (and specially in its > first iterations) the automated config editing tools might not > respect the comments as much as you would like, but that's a minor > thing that can be fixed later. > > 3- Making it hard to introduce confusion by skipping order. As an > example: > > server!port = 80 > server!limit_connections!per_second = 100 > virtualhost!bar = foo.domain.org > virtualhost!foo = bar.domain.org > virtualhost!bar!documentroot = /var/www/foo > virtualhost!foo!documentroot = /var/www/bar > virtualhost!foo!handler = cgi > server!handler = file > > What do I show here? Yes, for the parser there is no ambiguity - But > for somebody just glancing over, it will look fine - It will be hard > to spot that the 'bar' vhost points to /var/www/foo and 'foo' points > to /var/www/bar. Oh, and somebody at the very end just added that > the base handler should be 'file'. Well, that should be placed next > to the other 'server' entries! > Yes, it would easily be solved by demanding the configuration file > to be sorted alphabetically. But if you don't _require_ it (or else > just work but spew a warning, or something like that), people _will_ > get confused. And they will bitch and hate Cherokee. And we don't > want that. ;-) > > Greetings, > > It doesn't seem that human unreadable to me. And if it's difficult to differentiate between
virtualhost!bar!documentroot = /var/www/foo virtualhost!foo!documentroot = /var/www/bar you can use grep or something like that. Greetings, Armando. _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
