> > developers should not be writing anything to flash RAM.
> > That is something which is a user choice, and can only be done
> > with specialized utilities.
> > at all times the user initiates the process.
>
> I'd disagree with such a blanket statement. Some apps may be required to
> back up critical user data to flash as a normal part of the record editing
> process. Ideally this would still be somewhat under user control, such as a
> preference for "Back up changed records to flash memory?" or something like
> that.
there is absolutely NO reason to store critical user data anywhere BUT
in the place they were supposed to be stored. place them in the saved
preferences. when the user hotsync's, the data will be backed up.
now, if the user doesn't backup - it is *their* problem.
> I agree this should _not_ be done by 99.44% of applications, but there can
> definitely be demand for such extra data safety in certain enterprise class
> applications. A big company may well decide not to deploy 10,000 Palm
> devices to their sales force unless those devices can survive battery death
> or other mishaps, and then buy only flashable devices for this purpose. In
> this situation, I think flashing is a reasonable to feature to build into
> the application.
hotsync frequenty = solution to this problem. there is no other argument.
// az
[EMAIL PROTECTED]
http://www.ardiri.com/ <--- free games!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
