Hi, I'm working on an application that uses an editable text 'Field' to hold text that the user can edit. The user could indicate that this data is private (and should be encrypted).
My question is - while the user is editing the text in this field, the field (behind the scenes) may be resizing the memory buffer that holds the text - possibly copying it into a larger free block when it runs out of contiguous memory to support continued growth - or possibly releasing part of the block back to the heap after a large delete. Either way, the heap could end up storing fragments of the private data in unallocated memory... From a purist's point of view - is there a good way to clean all this up before control passes to some other application? So far, I haven't thought of one, since I don't see a way for my application to put hooks into the interactions between the field control and the memory manager(!). From a practical standpoint, I'm not sure how *real* the need is to develop an absolutely bulletproof solution - however, it's a puzzle, and I wondered if any of the experts in this forum would have some comments. Thanks in advance, Stephen -- Please remove no and spam from my email address if replying by email. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
