You have a few options. 1) Encode your state in XML, and download it separately. If things are set up correctly, the XML file will be stored in the browser cache. 2) Compile your data into a MXML application, and load it at runtime using the MovieClip.loadMovie() method, and dig into it through AS code. I think there might be some limits to max Model size in the current release, though. 3) Wait for the code I'm working on right now to get checked in and make it to a public release. :-)
-Roger Roger Gonzalez mailto:[EMAIL PROTECTED] > -----Original Message----- > From: sbyrne_dorado [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 05, 2004 3:20 PM > To: [email protected] > Subject: [flexcoders] "Almost" read-only client side cache > > In the application that we're developing, there is a significant > amount of state that the client side RIA uses that changes very > slowly. By very slowly I mean it may not change for a month, may go > through a few days where it changes more frequently, and then goes > dormant again. > > Rather than downloading this state each time the client side Flex > application is started, it would be useful to somehow persistently > cache that state on the client side. > > I'm looking for advice as to what the best practice for addressing > this need is. I can imagine a couple of possibilities, but I'm sure > there are better choices available: > > 1) arrange for the state to be written out on the server side when it > changes in the form of ActionScript classes or .mxml files, and > integrated into the core application somehow. When the user starts > the application the next day, Flex notices that the application has > changed on the server side and re-downloads it. This can be a pretty > big hit if the application is large (which ours is likely to be). > > 1a) A variant of 1, where the generated .as or .mxml file is not > incorporated into the main application directly, but is loaded using > some kind of deferred loading mechanism. > > 2) Using some client side storage mechanism, such as SharedObjects, > plus some versioning scheme. On startup a quick request or series of > requests to check for updates to the cached state is made, and any > available updates are loaded. This has the limitation of only allowing > 100k worth of state (w/o prompting the potentially naive user) -- this > may be sufficient, but it may not. Moreover, whether it will be > sufficient or not may depend on the needs of our customers, and may > not be something we can predict in advance. > > Can anyone suggest other options for achieving this goal? > > Steve > > > > ------------------------ Yahoo! Groups Sponsor > ---------------------~--> > Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar. > <br> Now with > Pop-Up Blocker. Get it for free! <br> http://companion.yahoo.com > http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/nhFolB/TM > -------------------------------------------------------------- > -------~-> > > > Yahoo! Groups Links > > > > >
