4 ms·
Think of it like this. Zed is combining Apache's nonstandard configuration language with it's internal runtime representation of such. He's doing it in a way
by adamtj 16y ago
Think of it like this. Zed is combining Apache's nonstandard configuration language with it's internal runtime representation of such. He's doing it in a way that's standard and manipulable at runtime. So changes to the runtime configuration are persistent. You can fix that. That's the beauty of it. It's an incredibly simple and flexible idea that builds upon existing, robust, and standard software. If you want to diff config files, then you could slap together an XML, JSON, or any other representation of your config data and write a loader for it.
- stesch 16y agoIsn't reading from sqlite all the time a bit bad for the performance?
- techiferous 16y agoWouldn't the server only read it after a config option has been changed? I don't think the server is going to check this database every time a request comes in.
- stesch 16y agoadamtj said "manipulable at runtime", so I guess he meant the changes are available directly after an UPDATE. How can you tell if the config is changed? You either poll it every time with SELECT (SQL) or see if the timestamp of the database file has changed. (If SQLite works this way. I never had the need to check on the file status.) This costs time as well. Other web servers have a config file and reload it after getting signalled. But: It's a bit early to say what Zed intends with SQLite. Maybe mongrel2 gets a configuration interface like Cherokee and only reads the DB on startup and after getting signalled.