[pclasses-devel] rethinking Mime

[stephan b. <st...@s1...>]

Yo!

We talked the other day about why Mime is currently in System. Here i 
will go through some properties of MimeType and MimeTypeDb, and try to 
figure out what module they belong to:

- Dependencies-wise, MimeTypeDb needs Plugin (or at least Factory) and 
some minimal i/o support to read the platform-dependent mime.types 
(std::iostreams will do), plus System::PathFinder (to provide several 
convenience functions). It does not need anything from Net, nor 
specifically from the IO module.

- Reading the mime.types is platform-dependent, and platform-dep code 
conventionally goes into System.

- MimeType itself is basically a Pair<String,String>, and provides no 
platform-specific functionality. 

- The idea of mime types is applicable to a range of things, from 
application dispatcher to classloading (app loading is only a special 
case of classloading). Keeping it as "low in the dependency chain as 
feasible" helps make it more accessible to clients.



Okay, so i will now argue the following:

MimeType ==> Core
MimeTypeDb ==> System (for deps/features reasons)

???

-- 
----- st...@s1...   http://s11n.net
"...pleasure is a grace and is not obedient to the commands
of the will." -- Alan W. Watts