Toni,
Read thread from Noam and myself on "generic wrapper page" and also consider
registering users to provide value added content, as well as maintaining
their language preferences.
You are right using session variables, when a user comes back to the site
after the default session timeout period their language preference will be
gone. Using cookies or client variables will be much more long term.
Cookies persist as long as you wish them to or until the user flushes the
cookies out of their browser cache.
Client variables will persist for a default of 90 _inactive_ days.
In the case of cookies, users must be able to accept cookie. In the case of
client variable the user must accept cookies otherwise you must put CFID and
CFTOKEN on the URL in order to maintain the users link to the client
variables.
Yes, you are potentially going to have a problem with hijacked client
variables if you include CFID and CFTOKEN on the URL. This is a decision
that you are going to have to make.
Regards
Stephen
> -----Original Message-----
> From: Toni Trape [mailto:[EMAIL PROTECTED]]
> Sent: 10 May 2001 15:32
> To: Fusebox
> Subject: RE: Advantages of use cfid and cftoken?
>
>
> First thanks to all of you, but i continue confused about my solution.
> Perhaps if i tell you my problem all of you can understand me better, and
> can give me the better solution.
>
> I'm developing some websites in fusebox and fusebox is a very good method
> to make websites, but i have a problem about the languages.
>
> These websites have more than one languages (english, french,
> spanish,...).
> In the first time we duplicated all templates for each lenguage, but any
> update in the website will force us to make it for each language
> templates
> so the mantenience of a website is very hard, specialy in
> websites that are
> in 3 or 4 languages.
> Then i discover fusebox. I was thinking that fusebox can solve
> this problem
> and i was trying to make something like this in index.cfm file:
>
> <CFCASE VALUE="list">
> <cfinclude template="qry_list.cfm">
> <cfinclude template="lng_list_#session.language#.cfm">
> <cfinclude template="dsp_list.cfm">
> </CFCASE>
>
> #session.language# is a variable that define the user language
> (choosed in
> homepage).
> I include a template lng_ that have some cfset's.
> <cfset text1 = "hello"> in lng_list_en.cfm
> <cfset text1 = "hola"> in lng_list_es.cfm
> And in dsp_ file i have <cfoutput>#text1#</cfoutput>
> So for each dsp file i have some lng_ files.
>
> Is good for:
> -the mantenience so i only have one dsp file
> -translate a website is only translate the lng files.
> Problems:
> -dsp templates code are more nasty and dificult to edit because have many
> cfoutput for each text.
> -The session variables expires with a timeout so if some person have a
> bookmark to one page can be possible the next time he go to this bookmark
> the session have expired so he will see the page in the default language,
> no in his choosed language.
>
> For this is for what i looking for a better solution than session
> variables.
>
> Toni
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
