I think we need a little more to go on. If you've looked at the current PalmOS devices, you've noticed heap and storage in the multi-megabyte range. This is 'usually' enough for most applications.
If you've looked, and the memory sizes concern you, then we really need to hear what you expect to do that can't be done in several megabytes. Otherwise, of course, read into heap, futz with it, write it back out. However, PalmOS databases are already in write protected RAM (or at least appear to be), which means that an app can efficiently write directly to a database record, assuming that's okay in your data model. If not okay, say a session embodies more than one related modification, you'd want to make all the changes to a session copy (not necessarily in heap) and post them in a more atomic way. On 2/5/07, dmw <[EMAIL PROTECTED]> wrote: > I'm new to Palm OS development, and I'm trying to get a handle on how to > manage program data. In the scenario of a simplistic desktop application, > one would store persistent data in a file, load that data in when the > program starts, work with the data in memory, and save it periodically and > at application shut-down. > > Since the Palm is a memory limited device, do you palm developers always > keep your persistent data in the database, without ever working with copies > of said data on the heap? Seems it would be difficult to manage, with every > operation being an opportunity for database corruption. What are the best > practices here? > -- > For information on using the PalmSource Developer Forums, or to > unsubscribe, please see http://www.palmos.com/dev/support/forums/ > -- yisdersomenimororsisasisdenderisorsis? Jeff Loucks -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
