In case anyone's interested, I ended up reworking this to having one remote proxy class. On instantiation, it receives a VO with info for the service delegate, as well as with the name of a "requester" proxy, which may be one of the "local" XML proxies. On return of the remote call, the remote proxy sets the data property of the requester proxy to that of the returned data and then removes itself from the facade.

Hi all,

I'm currently rebuilding a bit of a messy app using PureMVC (which I find intriguing). My question is about proxies -- this is an AIR app that reads in two XML files for most of the model. The XMLs are stored locally and initialized from there, but the user may download the XMLs remotely. Currently, I have that set up as a remote and local Proxy for each XML file. The remote Proxy is queried for new information and downloads the XML, after which it sets the local Proxies data object (my throw in some data manipulation in there). Only the local Proxy's model is shown in the views. What do you think of doing it this way? Is there a better way of doing it?