My Sup wants them to login once, and based on there permissions in the LDAP to be able to jump around to different department without having to login again(at least untill it timesout).
-----Original Message----- From: Randell B Adkins [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 2:50 PM To: CF-Talk Subject: RE: CfApplication Then allow them to log into the department application instead of the ROOT CFAPP. Is that possible? >>> [EMAIL PROTECTED] 06/11/02 02:48PM >>> Just because each department is really a different application, so I though i should have a different CFAPP name. Is this wrong? -----Original Message----- From: Randell B Adkins [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 2:44 PM To: CF-Talk Subject: Re: CfApplication Why do you need a different name for each department? >>> [EMAIL PROTECTED] 06/11/02 02:39PM >>> Hello, quick question. What is bad about your whole site, using the same CFAPPLICATION name? Right now I'm going to possibly have a CFAPP. name for each department. I validate users in the root CFAPP. and have to copy validation variables to the CFAPP. the user whiches to go to. If I used only 1 CFAPP. I would not have to copy varables across CFAPPS. -----Original Message----- From: Mike Brunt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 1:41 PM To: CF-Talk Subject: RE: How do Client Var Behave This is an interesting thread, (as they all are). If you are going to make something span <CFAPPLICATIONS it is probably logical and sensible to design it to span servers (for clustering/fail-over etc.) I would not use the Server scope for client vars, just my opinion. Would it not be more logical to store Client vars in a database and use Cookies to store id etc information at the client end. Your only gotcha here is to make sure that you set the datasource name in all Applications and/or Servers preferably using the Request scope. That is of course assuming the database is on a separate box accessible to all <CFAPPLICATIONS and Servers. This should also work even if all was on one box and clustering was not requied. Kind Regards - Mike Brunt, CTO Webapper http://www.webapper.com Downey CA Office 562.243.6255 AIM - webappermb "Webapper - Making the NET work" -----Original Message----- From: Brian Eckerman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 10:14 AM To: CF-Talk Subject: RE: How do Client Var Behave That are specific to a user..(Honestly this is really what client variables should do!!) -----Original Message----- From: Kreig Zimmerman [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 12:19 PM To: CF-Talk Subject: Re: How do Client Var Behave Use the "SERVER" scope. ----- Original Message ----- From: Brian Eckerman To: CF-Talk Sent: Tuesday, June 11, 2002 12:04 PM Subject: RE: How do Client Var Behave How would I declare a var that would span applications? -----Original Message----- From: Randell B Adkins [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 11, 2002 12:00 PM To: CF-Talk Subject: Re: How do Client Var Behave The client variables are unique to the application. Thus the client vars in APP1 are ONLY available to APP1 >>> [EMAIL PROTECTED] 06/11/02 11:57AM >>> Hello again. Got a problem. I declare an Application context(say APP1) with cfapplication. then I set some client variables... I then cflocation to anouther directory, with.. anouther declared Application context(say COOLAPP2) then I try to reference the client variables I set in APP1. --This Doesn't work-- :( My understanding is the whole point of Client varialbes is that they span application contexts. The above situation doesn't work...Is my understanding wrong? ______________________________________________________________________ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
