Hi Gunnar, hi Alvaro! :) On Friday 13 June 2008 17:35:07, Alvaro Lopez Ortega wrote: > On 13 Jun 2008, at 16:27, Gunnar Wolf wrote: > > Alvaro Lopez Ortega dijo [Fri, Jun 13, 2008 at 07:28:57AM +0200]: > > I just hate duplication ;-) I understand your point, but... Well, the > > MIME list table is not that huge, 764 lines long in my system. Maybe > > if Cherokee read it at initialization time and, as long as nothing in > > it is overriden in the configuration, uses the system-wide values? Of > > course, a similar initialization routine could be done for whatever > > convention other systems use. And its impact on the webserver itself > > is negligible, as it could be seen as part of the initialization > > process. > > > > Cherokee-admin could even report that "there are all those lines I > > cannot manage - Import them all? Import one of them?" > > > We must keep in mind that the server runs almost everywhere: Linux, > Solaris, OS X, BSDs, and even Windows. Every decision we make has to > work across all the platforms; that's why cherokee-admin is a web > application rather than a GTK+ one, for instance. > > There is something that we could do, though. How useful do you think > that would be to have an importer that only shows up in the > configuration Mime Page if /etc/mime.types is present?
If finally implemented, I would rather keep this handled in cherokee-admin instead of cherokee. Parsing the file is at launch time is trivial, but since Cherokee needs some more info as Alvaro said it would have to duplicate data anyway. Plus, keeping things in sync could be bothersome (what if some program modifies /etc/mime.types and does so erroneusly?). Not necessarily complex, but bothersome. If at launch time it can't handle things (doesn't understand a line, for example), then what? Ignore it? Launch the program anyway with an unknown list of MIME Types supported? Wait interactively for a fix?. Having things handled in cherokee-admin allows to fix these kind of things interactively, but having it in cherokee and launching a server with an unknown state (or aborting the program for something as trivial as a badly added MIME type) does not seem like a clean option to me. Just my 2cts. -- [EMAIL PROTECTED] http://unixwars.com _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
