Re: Tips on Saving Data?
Re: Tips on Saving Data?
- Subject: Re: Tips on Saving Data?
- From: Nathan Day <email@hidden>
- Date: Wed, 03 Dec 2003 08:46:18 +1100
I doing something like that in an application I am working on, every time there is a change a NSTimer is created to save the change later on, once the changes are saved I set the NSTimer intance varible to nil, that way every time a change occurs I can check to see if the timer has already been created and not bother. As for how often I'm still in developement stage and hve it set at a minute. Really you should never have to save until you program quiets, so it depends on how valuable your data is if something unexpected occurs, like power failure, since my program will never crash :|
On Wednesday, December 03, 2003, at 06:24AM, Demitri Muna <email@hidden> wrote:
>
Hello,
>
>
I had a question that I posted last week but got no responses for (may have been the holidays). I'll recast it, but in a much shorter way.
>
>
Let's say you have an application like iTunes. What is the recommended strategy for saving changes to the library (where there is no "Save" command)? Presumably you would not save after every little change, but how often is good? Is there a way to minimize drive/CPU time? It there a file format that is preferable in this case?
>
>
Thanks,
>
>
Demitri
>
_______________________________________________
>
cocoa-dev mailing list | email@hidden
>
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
>
Do not post admin requests to the list. They will be ignored.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.