Actually obtaining the data isn't the issue. I more interested how do I go about comparing the old data to the new data? Array, some sort of custom hash, or xml. Which is faster or better?
I would think array would be best by comparing old data array to new data array and then creating a third data array that holds all those that haven't changed? Yes all 500 objects are shown at once. The issue isn't getting the data its how slow and processor intensive it is to create the objects all over again if the data has changed. --- In [email protected], "Brian Deitte" <[EMAIL PROTECTED]> wrote: > > Caching of data across browser sessions, I assume? This is usually > done with SharedObject. But I wonder if there's a way to rearchitect > your application so this isn't needed? I assume that all 500 objects > aren't shown at once and that you could implement some kind of paging > mechanism. -Brian > > On Wed, Aug 6, 2008 at 3:17 PM, flexaustin <[EMAIL PROTECTED]> wrote: > > I was wondering if anyone has done any caching of data in Flex? And if > > so how did you do this? > > > > I have an application that pulls in up to 500 items and converts them > > to DTO's. The app then runs a routine, which generates objects based > > on those dto's. The generation of objects is very memory intensive so > > I need to reduce this to increase usability as right now the user has > > to wait until all 500 objects are created. I would like to be able to > > generate say the first 10 objects based off the old data, if the data > > hasn't changed since the last time the data was grab (via httpservice) > > then run the routine to create the other 490 objects. > > > > So sorting by saying N changed?...yes through out, N + 1 > > changed?....no keep create object, N + 2 changed?.... yes through > > out.....N+10 stop. > > Run...routine recreate the other 490 and stick them back in the > > correct order. > > > > Make sense? > > > > >
