Brad, Thanks for the input. While I like your suggestion, I actually need the cache to be used again in subsequent sessions (like a web browser would), so I can't use a temporary in-memory solution, but need to write the cache out to disk to save it for continued use.
Thanks! --Dave > (c) Convert them to jpegs or pngs in memory. If you're just caching > runtime only, make yourself a dedicated cache file. Have an image > wrapper class with a ref to the image, a ref to an open BinaryStream, > and a position and size of the object in the stream. To write it out, > just append to the stream, and nil out the picture reference. To read > it back in, set the position of the stream and read in the length. > Delete the cache file when your app quits. > > -Brad > > On Apr 18, 2006, at 1:18 PM, Dave Wooldridge wrote: > >> So with all of this mind, any thoughts of wisdom from experienced >> REALdatabase users on the two methods described above? Or are >> there some >> caching methods/options out there that I haven't thought of that >> are faster, >> more efficient? Speed is the crucial element here. > _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
