Thanks for the feedback! Hey, that can be arranged There should be a dedicated 'storicle' for PureMVC.

I have been working on a pet project for several months now, and launched it last night. It's a tribute to PureMVC in its most stringent form. Done in Flex and AMFPHP.

Please have a look on www.storicle.com. Premise: create a storicle, write a version, and challenge friends to improve it. Pretty empty at the moment, so any participation will be appreciated

Sounds great Joel, and thanks for the feedback. That's in line with what I had in mind changing. Maybe we could compare results when you're ready?

Just dropping in again to find out if anyone has found this useful yet? I've some ideas to modify and extend it. Any feedback at all? Anyone tried it out yet?

Um... let's see. I'm working on an application which accesses about 45 different external db tables with separate proxies. The amount is still growing. Both mediators and other proxies use this at various times. In effect, if one view (mediator) cleaned up the proxy, another one might still be using it, and might find itself pointing to a null data object. With this utility, usage of the proxy is managed, keeping reference to clients using the proxy, and then clears it up if there is no 'reservation' on the proxy. Hope this makes sense.

I created a utility for the PureMVC framework called PGProxyReservation. In short:

The PGProxyReservation utility is used to effectively flush proxies from their data when not in use. Whenever a view or another proxy requires the use of a proxy, it reserves it, and releases it when it's done. The utility automatically gets the proxy in an initialised state, as long as it implements IReservable. When no reservation is left for a particular proxy, the utility clears its data object. This is a huge advantage for applications that are heavily data reliant. It keeps your application leight-weight, keeping initialised only those proxies that are currently in use.

Attachment too big: You can download it at: http://blog.pietergrobler.com/node/4

Hope this is helpful. Drop me a line with questions or feedback. Thanks, Pieter Grobler.

What if you have a variable number of proxies (that change dynamically), that need to react on a global timer event? Since they don't listen, what would be the best approach in this case?

I have come up with a solution that allows proxies notifying each other. I posted an example on http://blog.pietergrobler.com/node/3. Basically, proxies subscribe to another via a service. It would be interesting to get feedback on whether this is good practice or not.

I will also be posting more on proxies whose service can be reserved. This enables large data sets to be sent to garbage collection when the proxy has no active reservation.