RTT wrote:
On 13-12-2011 19:21, Arno Garrels wrote:
We don't want to open and load a text file each
time a new type is found.
True, that would be dog-slow.
For the generality of the HTTP server applications, other than the 10
or 15 most common MIME types (that should always be in the
On 13-12-2011 14:43, Arno Garrels wrote:
I would not link headers with MIME types (in the same list) but rather
keep it clear and simple. This new class should also be usable from
other components such as the SMTP client.
Totally agree with that. Associating header elements to the content-type
Angus Robertson - Magenta Systems Ltd wrote:
If filling from the registry, better if the list is filled
dynamically when a not yet resolved file extension is requested.
Except that scanning a single registry node or file, allocating memory
for those nodes, and building indexes for them may
We don't want to open and load a text file each
time a new type is found.
True, that would be dog-slow.
We need to think about Linux/OSX, this will be first use of registry
access in ICS, I've already done some stuff to help decoding MIME email
content.
I agree that memory is needed for
On 13-12-2011 19:21, Arno Garrels wrote:
We don't want to open and load a text file each
time a new type is found.
True, that would be dog-slow.
For the generality of the HTTP server applications, other than the 10 or
15 most common MIME types (that should always be in the list) and the
