It's good to know it's getting looked at. I came across Ethan's blog before when I was looking at the issue and I came to the same conclusion he did before I ran out of time...
"It turns out I'm missing some details about the magic mojo required to get the Flex ModuleManager to recognize modules loaded via Loader.loadBytes(). It's not currently supported in Flex 3." Would it help if there was an enhancement request plus votes, or is this already in hand? Gk. Gregor Kiddie Senior Developer INPS Tel: 01382 564343 Registered address: The Bread Factory, 1a Broughton Street, London SW8 3QJ Registered Number: 1788577 Registered in the UK Visit our Internet Web site at www.inps.co.uk <blocked::http://www.inps.co.uk/> The information in this internet email is confidential and is intended solely for the addressee. Access, copying or re-use of information in it by anyone else is not authorised. Any views or opinions presented are solely those of the author and do not necessarily represent those of INPS or any of its affiliates. If you are not the intended recipient please contact [EMAIL PROTECTED] ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Alex Harui Sent: 11 June 2008 21:44 To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Flex 3.1 - The "Marshall Plan" It is being considered. Below is a comment from one of the main AIR guys: There will likely be a way to install modules incrementally, with some built-in validation of the module's signature. In fact, you can kinda do it now. If you know the hash of the module a priori, you can verify the module before calling loadBytes(). Or you could use XmlSignatureValidator to validate a module belonging to a "trusted" 3rd party. Also, check out my blog: http://weblogs.macromedia.com/emalasky/ <http://weblogs.macromedia.com/emalasky/> archives/2008/04/remote_plugins.html
