Storing info at Registry : Pros and cons????...

  • Thread starter Thread starter Vijay
  • Start date Start date
V

Vijay

Hi,
I want to store info at the client machine. The options available to me are
either store it in Windows registry or store it as cookie at client side.
Whats are the pros and cons. of storing information or preferences at
windows registry??
Whats consideration should be taken while storing any info at registry??
Thanks in advance?
Vijay
 
Vijay said:
I want to store info at the client machine. The options available to
me are either store it in Windows registry or store it as cookie at
client side.
Click to expand...

Hold on a minute ...

Cookies are used with web-based systems so, if you're looking at
clients running [only] a web browser, the Registry is out of bounds
straight-away. Your code, running within the browser, won't have
permission to go anywhere near the Registry.

If you're running an installed client application, you can use just
about anything you want to store the information.
Whats are the pros and cons. of storing information or preferences
at windows registry??
Click to expand...

The Registry is often protected from casual access - user's won't
be able to find (and change) the information but it is also notoriously
difficult to backup and recover [successfully] and inherently
non-portable so when the user gets a new PC, they'll lose all their
information (even /if/ you provide a utility to save it /elsewhere/
- the users won't run it).

If the data's not too sensitive, I'd just drop into into a file in the same
directory as the program (assuming it /is/ an installed program,
of course).

HTH,
Phill W.
 
Hi,
Thanks for the reply.
Iam creating an activex that will be downloaded in the client system and
will be running their. Can the activeX control access the registry(assuming
client is allowing my control to do so)????

I want to store client preferences on his machine only. what are the other
options available to do so...
Thanks,
vijay
Phill. W said:
Vijay said:
I want to store info at the client machine. The options available to
me are either store it in Windows registry or store it as cookie at
client side.
Click to expand...

Hold on a minute ...

Cookies are used with web-based systems so, if you're looking at
clients running [only] a web browser, the Registry is out of bounds
straight-away. Your code, running within the browser, won't have
permission to go anywhere near the Registry.

If you're running an installed client application, you can use just
about anything you want to store the information.
Whats are the pros and cons. of storing information or preferences
at windows registry??
Click to expand...

The Registry is often protected from casual access - user's won't
be able to find (and change) the information but it is also notoriously
difficult to backup and recover [successfully] and inherently
non-portable so when the user gets a new PC, they'll lose all their
information (even /if/ you provide a utility to save it /elsewhere/
- the users won't run it).

If the data's not too sensitive, I'd just drop into into a file in the
same
directory as the program (assuming it /is/ an installed program,
of course).

HTH,
Phill W.
Click to expand...
 
Back
Top