"Joe", >(Example Scenario: User installs 10 such apps, tries >them out, then deletes them. Each leaves a 1K file >behind. Now User has lost 10K and is not happy.)
If an application has a need to store anywhere close to 1K or more, it should put it in database (or preference) tied to its own creator ID so it gets deleted automagically. It does not take 1K to store security/registration related data. The saved and unsaved application preference databases already exist, so adding to them only allocates the incremental difference in the space required for the additional record(s) with the registration data. Since they are resource databases, it thus consumes 10 bytes per resource in the recordset list plus however many bytes are needed to store the encrypted data. I don't think it should be likely to ever need more than 50 bytes per app, and even that may be generous. Under 25 bytes including the 10 byte resource overhead should do it. The typical user would have a hard time knowing they lost 25 bytes, even after 10 such applications did the same thing. And while I don't necessarily like the idea of leaving behind garbage either, I sure like it better than thinking some shareware app is going to try reflashing a ROM behind my back. (Knew there was a reason I used Visors...) Doug -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
