Re: Package Proposal: Preference_Manager
| From: | Jon Wood | Date: | Mon, 16 Dec 2002 04:06:06 +0000 |
| Subject: | Re: Package Proposal: Preference_Manager | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-11692@lists.php.net to get a copy of this message | ||
Stig S. Bakken wrote:
On Sat, 14 Dec 2002, Martin Jansen wrote:+1 on this.On Fri Dec 13, 2002 at 10:3425AM +0100, Stig S. Bakken wrote:On Sun, 2002-12-08 at 22:30, Martin Jansen wrote:On Sat Dec 07, 2002 at 09:0645PM +0000, Jon Wood wrote:Jon Wood wrote:give it, it's a small class for managing user preferences in an application, with basic session based caching of the values, and the ability to get default values if the user wants it to.I'd like to propose a new package, and I'm looking for the right name to
How about Authentication/PrefManager?
Sounds ok for me.
Uhm, what do preferences have to with authentication?
That was my first thought also. But actually you need to authenticate the user in some way to load the preferences for him. Sure, but does that relation need to be reflected in the preference handling package? The way I see this, authentication is just a way of establishing identity, but a preferences package would be useful for managing per-package or per-application settings well as per-user settings. Binding the name to "auth" kinda limits the scope to users only. - Stig I see your point now... guess it must just be my limted view of what it might be used for :P I always imagined the class just being used to store user prefs, since that was the situation it was designed for, but your point about storing application settings is a good one... any ideas on a more suitable category name? Jon