On 21 Jul '08, at 10:09 AM, Lee, Frederick wrote:
I was thinking of keeping the User ID and other simple < 2KB of identifiers within the bundle. I found the LSEnvironment option and it 'appears' to be what I'm after.
What if there are multiple users on the machine? Then they'll all be forced to use the same user ID. Even worse: in many enterprise environments, applications are stored on a central file server that only network admins can modify. With your scheme, not only would users not be able to set their own user ID, but they wouldn't even have write access.
In general you should *never* modify the contents of your app bundle at runtime. (The only exception would be for apps that can software- update themselves, as with the Sparkle framework.) Any modifiable data should go in user defaults, or in the user's Library/Application Suppport/ directory. Data to be shared between users should go in / Library/Application Support/.
Also, *never* store passwords in regular files! Especially not files that can be read by other users! The Keychain is a secure place to store passwords and you should use it for that.
But FWIW... using XML based LSEnvironment had appeared to more... modular.
Modular how? (And user defaults are based on property lists just as the Info.plist is, though it really doesn't matter to the developer.)
—Jens
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list ([email protected]) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
