[THIN] Re: Developer Questions
- From: "Braebaum, Neil" <Neil.Braebaum@xxxxxxxxxxxxxxxxx>
- To: "'thin@xxxxxxxxxxxxx'" <thin@xxxxxxxxxxxxx>
- Date: Mon, 17 Feb 2003 16:37:55 -0000
I think there is (or at least should be) a clear distinction.
Per-user *configuration* data should ideally be in HKCU.
Per-user *data* should be somewhere that HKCU points to.
Clearly there are some applications that clearly work that way. And some
that clearly store too much of this "data" in HKCU. Some of Microsoft's
products are not exempt from this - although they do *tend* to follow this
reasonable rationale.
In short, the registry is not for significant amounts of data - nor were ini
files, previously. They are more for configuration information, that points
to where the (potentially) sizable data may well be.
Clearly over time, the application data folders within the profile structure
have hinted towards this sort of thing, given how they tend to be used.
Neil
> -----Original Message-----
> From: Tim Mangan [mailto:tmangan@xxxxxxxxxxxx]
> Sent: 17 February 2003 16:30
> To: thin@xxxxxxxxxxxxx
> Subject: [THIN] Re: Developer Questions
>
> A historical answer of what M$ recommended...
> - Win 3: Put it in system.ini
>
> - Win 3.1: Put it in a private ini file in the Windows root
> directory (system.ini is too crowded)
>
> - Win 95: Put it in the registry. (Windows root directory is
> too crowded) Usually meant HKRY_LOCAL_MACHINE.
>
> - Win NT: Put in HKEY_CURRENT_USER so we can have multiple logins.
>
> - Win XP/.NET: Stop putting into registry. Registry is too
> crowded (this may be related to what M$ is doing with the
> registry on Server 2003). If the information is machine
> specific, place in a app specific data file in the
> applications installed folder. If the info is use specific
> put the file into the user's profile area.
>
> Either HKRY_CURRENT_USER in the registry, or a private data
> file is the best method.
>
> Note: A developer doing anything with files on a server needs
> to learn about, and use the CSIDL. There are quite a number
> of CSIDL which are, basically, environment variables that
> point to the standard location on this machine and this user.
> For example, system root folder is CSIDL_WINDOWS.
> CSIDL_PROGRAM_FILES is usually "C:\Program Files". The
> developer should always query the value of the appropriate
> CSIDL rather than assume, for example, Windows is even
> installed on C:. The Developer should query CSIDL on MSDN for
> more info.
>
> For user-specific application data, the CSIDL is
> CSIDL_LOCAL_APPDATA (usually pointing to "C:\Documents and
> Settings\username\Local Settings\Application Data") is a good
> place to create an app specific folder to drop a file. This
> area is normally included in the roaming profile.
>
> -----Original Message-----
> From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On
> Behalf Of Schneider, Chad M.
> Sent: Monday, February 17, 2003 10:19 AM
> To: 'thin@xxxxxxxxxxxxx'
> Subject: [THIN] Developer Questions
>
> What is the Citrix recommended way of storing personal,
> unique application settings per user when running a Citrix
> app? Is a .ini file in the Windows folder the only way? For
> example, these are for like dialogs that have a checkbox on
> them that say something like a "Don't ask me this again" type
> of question. Where do I store that they checked this?
>
> Any answers to these would be helpful.
***********************************************************************
This e-mail and its attachments are intended for the above named
recipient(s) only and are confidential and may be privileged.
If they have come to you in error you must take no action based
on them, nor must you copy or disclose them or any part of
their contents to any person or organisation; please notify the
sender immediately and delete this e-mail and its attachments from
your computer system.
Please note that Internet communications are not necessarily secure
and may be changed, intercepted or corrupted. We advise that
you understand and observe this lack of security when e-mailing us
and we will not accept any liability for any such changes,
interceptions or corruptions.
Although we have taken steps to ensure that this e-mail and its
attachments are free from any virus, we advise that in keeping
with good computing practice the recipient should ensure they
are actually virus free.
Copyright in this e-mail and attachments created by us belongs
to Littlewoods.
Littlewoods takes steps to prohibit the transmission of offensive,
obscene or discriminatory material. If this message contains
inappropriate material please forward the e-mail intact to
postmaster@xxxxxxxxxxxxxxxxx and it will be investigated.
Statements and opinions contained in this e-mail may not
necessarily represent those of Littlewoods.
Please note that e-mail communication may be monitored.
Registered office:
Littlewoods Retail Limited,
Sir John Moores Building,
100 Old Hall Street,
Liverpool,
L70 1AB
Registered no: 421258
http://www.littlewoods.com
***********************************************************************
*********************************************************
This Week's Sponsor - RTO Software / TScale
TScale increases terminal server capacity.
Get 30-40% more users per server to save $$$ and time.
Add users now! - not more servers. If you?re using Citrix,
you must learn about TScale! Free 30-day eval:
http://www.rtosoft.com/Enter.asp?ID=79
**********************************************************
For Archives, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
http://thethin.net/citrixlist.cfm
Other related posts:
