> I hope Gyrus will be ready for his exam, now.
Learning by the minute :)
- Gyrus
~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/f
th from a business perspective, but
a perhaps a nightmare from a programmer's point of view.
I hope Gyrus will be ready for his exam, now.
Taking cover!
Marianne
-Original Message-
From: Kwang Suh [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 15, 2001 7:11 PM
To: CF-Talk
S
--- Freddy <[EMAIL PROTECTED]> wrote:
> Let me see. A scalable app that uses session
> vaiables? Try an application that
> delivers personalized content. Store a cookie that
> logs the user in on entry to
> the site. It then retrieves a list of links, images,
> and pertinent user info
> that is st
> Curious - would switching from session vars to
> client vars entail
> a major rewrite? Am I dumb in thinking you'd just do
> a search for
> "session." and implement the client variable code?
Well, of course it depends. But since most people
wrap their session stuff around locks, and other
vari
> I think the overarching requirement for most, if not all, enterprise-class
> applications are reliability and availability. I can't see how using
> session vars meshes with this requirement. Hey, if all someone's making
are
> small apps, go right ahead and use session variables. Just don't ex
Let me see. A scalable app that uses session vaiables? Try an application that
delivers personalized content. Store a cookie that logs the user in on entry to
the site. It then retrieves a list of links, images, and pertinent user info
that is stored in session variables. If the user moves to a di
- Original Message -
From: "Freddy" <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Thursday, November 15, 2001 5:16 PM
Subject: Re: Session and Client Variables
> Kwang Suh wrote:
>
> > > My heart goes out to you! You so
Kwang Suh wrote:
> > My heart goes out to you! You sound like you've had a bad experience with
> a
> > session variable cult, or something. But if used in its proper context,
> > session variables can change your (work) life.
>
> Yeah, but what's "proper context"? Do people even bother to do
Daye
>
> -Original Message-
> From: Kwang Suh [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 14, 2001 8:07 PM
> To: CF-Talk
> Subject: RE: Session and Client Variables
>
>
> Yikes!
>
> The key differences between client and session variables are:
>
>
-
From: Kinley Pon [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 14, 2001 5:38 PM
To: CF-Talk
Subject: Re: Session and Client Variables
sounds about right! - Kinley
>From: "Gyrus" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: CF-Talk <[EMAIL PROTECTED
on variables. Just say no.
-Original Message-
From: Kinley Pon [mailto:[EMAIL PROTECTED]]
Sent: November 14, 2001 5:38 PM
To: CF-Talk
Subject: Re: Session and Client Variables
sounds about right! - Kinley
>From: "Gyrus" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROT
al Message-
From: Gyrus [mailto:[EMAIL PROTECTED]]
Sent: 15 November 2001 02:47
To: CF-Talk
Subject: Re: Session and Client Variables
> And yes, client variables DO "time out".
What's the timeout period? I wasn't aware of this, would
be nice to know for when I do u
rsday, 15 November 2001 12:47 PM
To: CF-Talk
Subject: Re: Session and Client Variables
> And yes, client variables DO "time out".
What's the timeout period? I wasn't aware of this, would
be nice to know for when I do use them.
> Bottom line: session variables suck.
> And yes, client variables DO "time out".
What's the timeout period? I wasn't aware of this, would
be nice to know for when I do use them.
> Bottom line: session variables suck. I hate them. They are the bane of
> CF. I hate how people put gigantic structures in session variables and
then
>
t say no.
-Original Message-
From: Kinley Pon [mailto:[EMAIL PROTECTED]]
Sent: November 14, 2001 5:38 PM
To: CF-Talk
Subject: Re: Session and Client Variables
sounds about right! - Kinley
>From: "Gyrus" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: C
sounds about right! - Kinley
>From: "Gyrus" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: CF-Talk <[EMAIL PROTECTED]>
>Subject: Re: Session and Client Variables
>Date: Wed, 14 Nov 2001 18:26:41 -
>
> > Hi Folks, i'm prepping fo
2001 18:27
To: CF-Talk
Subject: Re: Session and Client Variables
> Hi Folks, i'm prepping for the cf exam and i'm lacking a good
understanding
> of the difference between client and session variables. It seems that
> they both are capable of doing the same thing. When and why
&
> Hi Folks, i'm prepping for the cf exam and i'm lacking a good
understanding
> of the difference between client and session variables. It seems that they
> both are capable of doing the same thing. When and why should/would i use
> one or the other? What apps have you used client vars for and not
To: CF-Talk
> Subject: Re: session and client variables
>
>
> All you appear to be doing is reading and writing the cookies.
>
> Exactly how does this stop the user closing the browser and
> not having the
> cookie's destroyed?
>
> When the user re-start
: Re: session and client variables
All you appear to be doing is reading and writing the cookies.
Exactly how does this stop the user closing the browser and not having the
cookie's destroyed?
When the user re-starts the browser and goes to that page, the cookies still
exist (as far as I can
EMAIL PROTECTED]]
Sent: 01 June 2001 16:25
To: CF-Talk
Subject: Re: session and client variables
If you set the cookie with no expire time, the cookie is destroyed when the
browser closes, in both IE and NN. Now, the security for the app should be
that both session on server and cookie on client mu
ssage-
From: Andy Ewings <[EMAIL PROTECTED]>
To: CF-Talk <[EMAIL PROTECTED]>
Date: 01 June 2001 16:47
Subject: RE: session and client variables
>Paul
>
>Put this in your application.cfm:
>
>
>
>
>
>
>
>
>This will ensure that whenever the
If you set the cookie with no expire time, the cookie is destroyed when the
browser closes, in both IE and NN. Now, the security for the app should be
that both session on server and cookie on client must be present for there
to be a logged in condition. If either is missing, a login must occur.
Paul
Put this in your application.cfm:
This will ensure that whenever they close the broswer the session is killed
(or rather their link to the set of client vars is broken). The client vars
weill then get destroyed when the timeout is reached.
-Ori
24 matches
Mail list logo
