Alvaro Lopez Ortega dijo [Fri, Jun 13, 2008 at 07:28:57AM +0200]: > > The keys here are 'most' and 'similar'. We cannot relay on something > that most of the Unix system have, or that is similar among them. It > would be a mess. > > Besides, when we used the global mime.type we hit a couple of > important issues. For instance, we could not define "Max-Age" custom > values for its entries. So if we wanted to support the feature, > (...) > There is something that might help though. When the user adds a new > Mime entry, Cherokee-admin could read the system mime.types (if > present) and show the entries in the system file that are not > configured in cherokee so the user could pick from a list instead or > writing the mime type. It's not the perfect solution, but it is a > step closer.
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?" Of course, I'm currently not backing it with any code - but what do you think about it? -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF _______________________________________________ Cherokee mailing list [email protected] http://cherokee-project.com/cgi-bin/mailman/listinfo/cherokee
