Usage of flash.utils.describeType can be expensive, consider caching the results.

[GoogleCodeExporter]

When using flash.utils.describeType to describe a large class can be improved 
if the results are cached for later use. Borrowing from the Flex SDK, usage of 
DescribeTypeCache and DescribeTypeCacheRecord (minus the Flex SDK 
dependencies) can improved performance.

Original issue reported on code.google.com by pete...@gmail.com on 19 Feb 2010 at 9:45

Attachments:

• ClassUtils.as
• DescribeTypeCache.as
• DescribeTypeCacheRecord.as
• MetadataUtils.as
• ObjectUtils.as

[GoogleCodeExporter]

Update to DescribeTypeCache to 
getDefinitionByName("mx.binding::BindabilityInfo");

Original comment by pete...@gmail.com on 22 Feb 2010 at 10:46

Attachments:

• DescribeTypeCache.as

[GoogleCodeExporter]

Hi, we have no need to cache the describeType result since it is only used once 
for each Type that is created. The Type instances themselves get cached, so for 
each call to Type.forInstance()/forName()/forClass() there's only one call to 
describeType().

Original comment by ihatelivelyids on 10 Nov 2010 at 9:16

• Changed state: Invalid