Bug 290431 - [Content Type] Enhance scalability of ContentType description process
Summary: [Content Type] Enhance scalability of ContentType description process
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-24 11:52 EDT by Pawel Pogorzelski CLA
Modified: 2017-07-12 07:18 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pawel Pogorzelski CLA 2009-09-24 11:52:39 EDT 
Bug 182337 shows that current design of org.eclipse.core.contenttype.contentTypes extension point lacks scalability.

This is because each contributed content type can declare it's own describer. Since describers are customizable they are instantiated one per each type. During the process of determining the content type each one of these instances parses the input which introduces a great performance hit.

Bug 182337 narrows the problem to few classes responsible for describing XML files. This one aims at solving it comprehensively.
Comment 1 Pawel Pogorzelski CLA 2009-12-11 07:10:38 EST 
Removing target as a result of development plan update.
Comment 2 Mickael Istria CLA 2017-07-12 07:18:58 EDT 
Do you have a proposal of how to improve the scalability, but still provide the power of the ContentTypeDescribers?