Thanks Darshan, that's quite logical and simple indeed.

You talking about something Simon hasn't posted yet Cliff ?

I've got another question : if there's a FlexModule, why isn't there a FlashModule ? I bet I missed something but I don't want to have to subclass anything related to Flex since my front end is AS3 only. Should I create a FlashModule class inspired by the FlexModule ? Any idea ?

My thoughts exactly, though I do not have a player delivered to thousands of websites. :p

There is a solution that is likely to work (but it's still random) : you wait till your module is supposedly clear of any reference and then force a GC upon the application. Found on Simon Bailey's blog.

I read on the blog of Skinner that "You can load content SWFs from a subdomain. This will place it into a security sandbox implicitly". Though I wonder if it could affect communication between the app and the modules...

Hey guys,

I wanted to thank you both for the awesome job on Fabrication. I understand the concept of pipes and all but it was just too complicated to implement with several modules. Then I stumbled upon your framework and it helped a lot.

In regards to the problems of GC modules, maybe you haven't seen that already but there is a bug with Flash Player 9 : it doesn't really GC when it should do so upon dynamically loaded SWFs. Basically, the unload() method destroys the reference to the SWF but lets it run anyway. Without reference, it is very likely that the GC will miss sweeping the SWF.

The good news, well sort of, is that Adobe added a new method called unloadAndStop() that attempts to resolve some of the problems described by Grant Skinner. It is only available with Flash Player 10.

This problem may end up being a huge one for my project as I'm building a mid-sized Flash web site and I thought I'd break it into several swfs, one for each section. Well now I'm wondering if I should revert back to single core...What a pain.

I hope it helped and wasn't totally out of line.