Why is a command line change to ~/Library/Preferences/com.apple.LaunchServices.plist not effective immediately?

Question

When the Info window of Finder is used to associate files of a particular type with an application:

• the preference is effective immediately.

When Terminal is used to make a comparable addition to ~/Library/Preferences/com.apple.LaunchServices.plist

• the preference is not effective immediately.

Question

Why does Launch Services not immediately respect a write to the user's com.apple.LaunchServices.plist?

An ideal answer might be a reference to a page in the Apple Developer area.

Answers need not involve running a command.

Background

Agent or daemon?

Wondering whether a daemon or agent makes changes to that .plist effective, I ran:

sudo launchctl list

In the list, under the label heading, I see nothing that might relate to Launch Services.

References

An answer to Stack Overflow question How to set default application for specific file types in Mac OS X? suggests:

… to be reloaded. You can logout, wait a few minutes or force launchservices to restart …

In my case:

• log out did not have the desired effect
• I used the lsregister approach, but that type of scan is time-consuming.

The accepted answer to Super User question Is there a faster way to change default apps associated with file types on OS X? suggests:

… restarting the OS to apply changes (logging out and back in isn't enough) …

— if a restart suffices, that's probably less time consuming than killing then seeding the Launch Services database.

Answer 1

From Apple’s Launch Services Programming Guide (all emphasis mine):

All applications available on the user’s system must be registered to make them known to Launch Services and copy their document binding and other information into its database. It isn’t ordinarily necessary to perform this task explicitly, since a variety of utilities and services built into the Mac OS X system software take care of it automatically:

• A built-in background tool, run whenever the system is booted or a new user logs in, automatically searches the Applications folders in the system, network, local, and user domains and registers any new applications it finds there. (This operation is analogous to “rebuilding the desktop” in earlier versions of Mac OS.)
• The Finder automatically registers all applications as it becomes aware of them, such as when they are dragged onto the user’s disk or when the user navigates to a folder containing them.
• When the user attempts to open a document for which no preferred application can be found in the Launch Services database, the Finder presents a dialog asking the user to select an application with which to open the document. It then registers that application before launching it.

In spite of these automatic registration utilities, it may sometimes be necessary to register an application explicitly with Launch Services. For example, although developers are encouraged to package their applications so that they can be installed by simply dragging them onto the user’s disk, some applications may require more elaborate custom installer software. In such cases, the installer should call one of the Launch Services registration functions LSRegisterFSRef or LSRegisterURL to register the application explicitly.

Note the API calls needed by the only named manual registration procedure (source not available on opensource.apple.com, I’m afraid).

While working around a bug in processing of Launch Services on Leopard with FileVault enabled, I noticed that ~/Library/Preferences/com.apple.LaunchServices.plist is:

• processed only on login after boot, as input data to the buildup of the Launch Services database proper (FileVault-enabled Leopard often failed to do this step, resulting in seemingly lost user settings); and

• cached as long as the machine is not rebooted.

Simply put, it’s the user domain persistence layer of Launch Services, and modifications to that persistence layer are only acknowledged on next processing – reboot or reseed.