This has nothing to do with client variables. Cold Fusion uses the Registry
a great deal itself internally. For example, all datasource info, scheduled
tasks, etc...
--
Archives: http://www.mail-archive.com/cf-talk@house
9:09
To: [EMAIL PROTECTED]
Subject: RE: Client storage (RE: ColdFusion 4.0.1/SPARC/Solaris help
sought - registry corruption and cf scheduler problems)
This has nothing to do with client variables. Cold Fusion uses the Registry
a great deal itself internally. For example, all datasource i
Well, yeah, using client variables in the registry certainly won't help, but
the point is that the registry on Solaris is fubar (we won't get into NT.)
I'm not saying everyone should start refreshing their registry every day...
I'm saying that it's not difficult at all to find yourself with a very
eldon
http://www.desertraven.com/
Make a fast friend, adopt a greyhound!
-Original Message-
From: Ed Toon [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 06, 2000 22:09
To: [EMAIL PROTECTED]
Subject: RE: Client storage (RE: ColdFusion 4.0.1/SPARC/Solaris help
sought - registry corrupt
> If you're using client vars, get them into a database. If
> you're not using them, make absolutely sure they're not enabled
> anywhere.
I'd like to strongly second this recommendation. No one, under any
circumstances, should store client variables for an application within the
registry. The
> This has nothing to do with client variables. Cold Fusion
> uses the Registry a great deal itself internally. For example,
> all datasource info, scheduled tasks, etc...
Most of this is done when the service starts up, and reads the data from the
Registry.
The Registry isn't designed to stor
6 matches
Mail list logo
