--- Adam Judson <[EMAIL PROTECTED]> wrote:
> On 12/03/06, Eric H. Jung <[EMAIL PROTECTED]> wrote: > > > I want to serialize _data_ to a file so the user doesn't have to re-enter > > settings across > brower > > invocations. > > Do you care/need to know if the data is corrupted? > No. > Do you care/need to know if the data is maliciously changed to include > new functions that will now run inside chrome in your extension? > No. > Other things, e.g. custom XML, are (marginally) more difficult that > toSource()/eval() but in some cases it may be the right thing to do. > Make sure you've thought about it if it will be hard to change your > implementation later. > > I also found that writing import/export to XML code forced me to think > about the data structures I was using, which turned out to be a good > thing. > Thanks. I've already been through that exercise and am now trying to get rid of the XML import/export code in place of toSource()/eval(). > A > _______________________________________________ > Project_owners mailing list > [email protected] > http://mozdev.org/mailman/listinfo/project_owners > _______________________________________________ Project_owners mailing list [email protected] http://mozdev.org/mailman/listinfo/project_owners
