Comment Re:Innovatory Micro$loth? (Score 1) 712
I think the motivation for this is to be found in a new behaviour in win2k and an already announced intention.
Win2k allows each "application" to have private versions of shared libaries, ie to improve overall reliability and resilience by not allowing applications to update common files.
However if 20 apps install private versions of the same shared library, disk space would dwindle to nothing very soon.
So this appears to be a scheme to allow apps to have "seperate" links to common libaries. So if a new version of an app updates a libary for compatability reasons, that copy is not imposed on all of the other apps in the system. Essentialy the linkage is "branched" when the opdated libary is written onto the link.
Win2k allows each "application" to have private versions of shared libaries, ie to improve overall reliability and resilience by not allowing applications to update common files.
However if 20 apps install private versions of the same shared library, disk space would dwindle to nothing very soon.
So this appears to be a scheme to allow apps to have "seperate" links to common libaries. So if a new version of an app updates a libary for compatability reasons, that copy is not imposed on all of the other apps in the system. Essentialy the linkage is "branched" when the opdated libary is written onto the link.
