[interfacekit] Re: MimeDatabase
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: interfacekit@xxxxxxxxxxxxx
- Date: Wed, 21 Aug 2002 10:36:43 +0200 (MET DST)
On Wed, 21 Aug 2002, Ingo Weinhold wrote:
> Just to prevent you running out of work: You might also want to think
> about what additional MIME database related structures we need to
> maintain in the registrar. The quite vague `app meta MIME' comes to my
> mind, but I suspect, it will turn out, that this just denotes the sum
> of application specific MIME data (supported types, icons for
> types,...) only stored in attributes as the other data. Then there is
> `__mime_table' which is certainly also held in memory to speed up
> BMimeType::GetSupportingTypes(). This map must be kept in sync when
> changes to the database are done. I think, this does basically concern
> BMimeType::Delete() and BAppFileInfo::SetSupportedTypes() (watch out
> the private BMimeType::{Set,Get}SupportedTypes(), that we may or may
> not want to implement as well).
And a list (or BMessage?) with all installed types to speed up
BMimeType::GetInstalledTypes() would be a good thing, too.
CU, Ingo
- References:
- [interfacekit] Re: MimeDatabase
- From: Ingo Weinhold
Other related posts:
- » [interfacekit] MimeDatabase
- » [interfacekit] Re: MimeDatabase
- » [interfacekit] Re: MimeDatabase
- » [interfacekit] Re: MimeDatabase
- » [interfacekit] Re: MimeDatabase
- » [interfacekit] Re: MimeDatabase
- » [interfacekit] Re: MimeDatabase
- » [interfacekit] Re: MimeDatabase
- » [interfacekit] Re: MimeDatabase
- » [interfacekit] Re: MimeDatabase
- » [interfacekit] Re: MimeDatabase
- » [interfacekit] Re: MimeDatabase
- [interfacekit] Re: MimeDatabase
- From: Ingo Weinhold