mime.conf vs. mime.types

        Just out of curiosity, is there any reason Cherokee
uses
its own format in mime.conf instead of following the same
format
which Apache and other Unix applications have settled upon
using
in mime.types?  The reason being, the version of mime.types
shipped with Debian seems to be far more complete than the
mime.conf shipped with Cherokee.

        I'll assume here that people other than myself also
have
a file /etc/mime.types (or some equivalent) even though they
are
not necessarily running Debian.

-- 
Mark Nipper                                               
e-contacts:
832 Tanglewood Drive                               
nipsybitgnome.net
Bryan, Texas 77802-4013                     http://nipsy.bitgnome.net/

(979)575-3193                      AIM/Yahoo: texasnipsy
ICQ: 66971617

-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GG/IT d- s++:+ a- C++$ UBL++++$ P--->+++ L+++$ !E---
W++(--) N+ o K++ w(---) O++ M V(--) PS+++(+) PE(--)
Y+ PGP t+ 5 X R tv b+++ DI+(++) D+ G e h r++ y+(**)
------END GEEK CODE BLOCK------

---begin random quote of the moment---
cult: (n) A small, unpopular religion.
religion: (n) A large, popular cult.
----end random quote of the moment----
_______________________________________________
Cherokee mailing list
Cherokeelists.alobbs.com
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee

Mark Nipper wrote:

 > Just out of curiosity, is there any reason Cherokee
uses its own
 > format in mime.conf instead of following the same
format which
 > Apache and other Unix applications have settled upon
using in
 > mime.types?  The reason being, the version of
mime.types shipped
 > with Debian seems to be far more complete than the
mime.conf shipped
 > with Cherokee.

   You are right. We have been using a different file
without a real
   reason. Actually, Rodrigo and me were speaking about how
to change
   the parser in order to improve the MIME support some time
ago.

   If we change the file format we must look for a way in
which support
   the cache expiration period value.  In the current
configuration
   file, you can define types like:

=====
image/jpeg {
   max-age 1800
   suffixes jpg, jpeg, jpe, jfif
}
=====

   which means, the "image/jpeg" files that are
sent by this server can
   be cached for 1800 secs in a proxy cache.

 > I'll assume here that people other than myself also
have a file
 > /etc/mime.types (or some equivalent) even though they
are not
 > necessarily running Debian.

   What we thought was to use the FreeDesktop MIME file:

     /usr/share/mime/globs

   Don't ask me why did we think of using the FreeDesktop
one. I guess
   it is due our jobs: Both of us work in GNOME related
projects, so it
   was a kind of natural choice..

   Actually, I'm hesitating if this is the right choice for
Cherokee.
   IMO, it makes more sense to use /etc/mime.types because
it doesn't
   depend on a desktop related files.

   So, Mark.. you have opened the Pandora box!  lets
start thinking
   of how to improve the mime configuration files. We have
many
   questions to clarify:

     - Which format to use
     - How to manage the "max-age" value?
     - Should we ship a mime file and install it in case the
system
       lacks it?

     .. more?

-- 
Greetings, alo.
http://www.alobbs.com
_______________________________________________
Cherokee mailing list
Cherokeelists.alobbs.com
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee