The issue, normally, is one of maintaining "state" of a visitor among 
different interactions of the visitor's browser and the CF server

So, each browser request must pass something to the server with each 
browser request, so the server can identify the user.

Your best choices are:

   cookies

   Tokens

   form or URL variables.

But, you don't really need to maintain any information about the 
user... you just need to know the status of his machine (browser 
plugin) for each request.

So, why burden the application with the overhead of sessions, cookies 
and the like?

The simplest way would be to pass a hidden form field with each page 
request (flash or html) to the server.

In effect you are maintaining state at the client.


HTH



At 5:47 PM -0500 2/2/01, Evan Lavidor wrote:
>A what would/what do you do question:
>
>We are developing a site that's got some flash elements.  For the non-flash
>people, there will be html elements that swap into those places.
>
>I'd *like* to do a flash detect and then set a variable based on the results
>and then do something like
>
>       if flash IS 'yes'
>               insert flash header
>       else
>               insert html header
>
>
>But, I'm concerned about what variables I can use.  Here's my thinking.
>
>1. Session variables expire, so I don't want to use those.  Since I don't
>want to have to push a user back to a flash detect again.
>
>2. Cookies are probably my best bet.  Then I wouldn't even need to use the
>flash detect if they come back again.  But what if someone has cookies
>disabled?
>
>3. Client variables have the same problem, right?  If a user has cookies
>disabled, client vars won't get set.
>
>4. CFID and CFTOKEN lend themselves to the same problem, right?
>
>
>So, here I am wondering what I can do.  If I'm wrong on #3 or #4, then I'm
>okay, I suppose.  I could also pass an id in the url from page to page, but
>I'd prefer not to if I can avoid it.
>
>Any advice or thoughts is greatly appreciated.
>
>Thanks,
>
>Evan

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to