I'm debugging on the Treo 650 finally and attempting to make the app NVFS proof and have a few questions.
Basically, I can't afford to ever lose any user entered data if the device crashes, so I find myself calling DmSyncDatabase after each set of writes. The performance isn't too bad, but is there any drawbacks to calling this sync "very" often? Also, is there any way to bypass this whole caching mechanism and just write directly to the NAND memory? Read caches are fine but I'm not understanding the logic of write caching. Do I need to sync after DmResizeRecord and DmRemoveRecord calls? It amazes me that an OS would consider it safe to sync writes back to permanent storage only on application sleep or closing - especially on an OS such as PalmOS that is SOOO easy to crash. For example, I just found a bug on the Treo that has never showed up on any other device. Basically it was a 1 byte buffer overrun that reset the device without even a fatal alert. (-; -Dave -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
