ios - Why Apple suggests use your own NSFileManager when you use NSFileManagerDelegate? -
in apple docs of defaultmanager say:
this method returns same file manager object. if plan use delegate file manager receive notifications completion of file-based operations, should create new instance of nsfilemanager (using init method) rather using shared object.
i want know why suggest use new instance of nfilemanager when use delegate of file manager?what's wrong if use shared file manager this?
the thing can see delegate object receive lot of notifications don't want know, else?
your last paragraph pretty it. if set delegate on shared file manager, delegate ends getting called way more want. creating specific instance of nsfilemanager , setting instance's delegate, know delegate methods being called specific use of file manager , not of default uses.
keep in mind default file manager instance used lot more own code. lots of other libraries , frameworks using well.
Comments
Post a Comment