You're right on the SharedObject deactivation. This was definitively a bad idea, sorry. I want to introduce this because I'm currently working on an application running in two different SWFs, I need and use the SharedObject to store VOs and use the same proxys classes in the two SWFs to access data, I found this elegant. But in the same application, finally it's like using a global context, quite a bad practice.
>This sounds interesting; is the term "module" here used in the Pipes context or in the context of
>a Facade like UserInfoFacade which would be dedicated to managing user information, expiring sessions etc.?
You can use modules without pipes, even if pipes are recommended to let modules communicate http://trac.puremvc.org/Demo_AS3_MultiCore_Flex_Modularity
. It's rather easy to integrate Pipes when you already have integrated modules with a clean API for each.
>On a related note, I hope it isn't an anti-pattern to have a facade which isn't related to a concrete view per-se?
I recently have asked this on the forums, Cliff answered it here : http://forums.puremvc.org/index.php?topic=1445.0