> 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 be more efficient in one function. We don't want to open and load a text file each time a new type is found. I agree that memory is needed for all the MIME types, so it probably wants to be a global object shared between multiple servers, maybe with the existing code left as a default. I was only planning on checking: [HKEY_CLASSES_ROOT\MIME\Database\Content Type Not the full classes root. I was also thinking about two indexes, one of MIME types actually used, the other the hundreds or thousands that are actually registered. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
