Why are you structuring your app that way though? CFAPPLICATION should be
used to define the scope of one application, not the scope of a permission.
I suggest a different approach on structing the permissions part of your
web. If you're interested, contact me!
And to answer your questionY
Try storing your need information in a central database that all the
application can share.
Shawn Regan
-Original Message-
From: Brian Eckerman [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 12, 2002 1:05 PM
To: CF-Talk
Subject: Does cfcookie depend on cfapplication
Hello, this is my
> I though CFCOOKIE would be my Holy Grail because (I thought)
> they would be specific to one user, and span CFAPPLICATIONS.
Well, cookies don't have anything to do with CFAPPLICATION tags, so they may
work for you in this situation. Cookies are associated with a specific
virtual server, by def
I am not sure.. why you are doing all the below..
Cant you just create roles in a database based on LDAP
and have one CFAPPLICATION?
Another one.. Create Session Structures depending
on how many applications you might wanna have.
eg.. Session.AppOne, Session.AppTwo in one Application.
Joe
---
4 matches
Mail list logo