We have a CF server that has 4 or 5 applications that query our LDAP server.
The most used of these apps is our main user directory. Our networking folks
recently added monitoring software on our new LDAP server and they noticed that
there are over 2000 tcp socket requests (in the course of about
You could use an NTFS hardlink (junction) for this. I don't know the exact
details, but it'd work.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mischa
Uppelschoten ext 10
Sent: Tuesday, March 18, 2008 5:42 PM
To: Web Site
Subject: re[4]: [ACFUG Discuss]
Well, the fix didn't do it. I'm beginning to think bug.
Problem #1
Create this cfc and point a virtual directory to it. The website root for the
site containing the virtual directory has a different application.cfm than the
website that has this test component in it's physical structure.
Thanks Cody! I tried your suggestion, but the component is then executed
without any application.cfc "context", so my session vars are still not
available :-(
: I am not sure what the best practice is, but the following setup may solve
: your issues:
: Components\MyComponent.cfm
: Site1\appl
: : > All,
: : > I'm running into an issue with CF8 and how components are bound to form
: : controls. Proper execution of one of my components depends on a value in
: the
: : session scope.
Well, supposedly it was a known issue:
"70775 ColdFusion Ajax components cannot access CFCs in a virt
Thanks, Darin. There was a slight bug in the code you sent, which is that
Sesion.loggedIn has to be lower case for JavaScript to recognize it as a
Boolean keyword. That's fixed in the version below:
var isStillValid = #LCase(Session.LoggedIn)#; //
function checkStatus(){
if(!is
Thanks Cameron! Unfortunately, you cannot bind to a component using a mapping
combined with the cfc format:
"Using bind expressions
To specify a bind expression, use one of the following formats:
* cfc:componentPath.functionName(parameters)
Note: The component path cannot use a mapping.
Since you are on CF8, you might get an advantage from dynamically
setting the mappings. I usually drop common components into a
location below the wwwroot and refer to them using a CF mapping. The
technique below also allows you to move code server to server without
managing any mappings in the C
I am not sure what the best practice is, but the following setup may solve your
issues:
Components\MyComponent.cfm
Site1\application.cfm (-> this.name = "site1";)
Site1\Components ... this is an IIS virtual directory that points to >
Components
Site1\UseComponentToShowSiteNameOnSite1.cfm
Si
All,
I'm running into an issue with CF8 and how components are bound to form
controls. Proper execution of one of my components depends on a value in the
session scope.
Site1\application.cfm (-> this.name = "site1";)
Site1\Components\MyComponent.cfm
Site1\UseComponentToShowSiteNameOnSite1.cfm
10 matches
Mail list logo