Any good way to maintain server variables?

[Thompson, Ryan K (James Tower)]

We are implementing a clustering solution that can do sticky session but it
needs a unique value 
it either a cookie variable or URL variable per server. Rather that changing
the code on each server I'd like to use 
a variable that would be unique on each server. Does anyone know of a good
way to set and maintain a 
server or cgi variable to do this?

The domain name will not change in the HTTP header so we can't use that. I
thought of putting a browser in the startup 
of each server to hit a page but when CF restarts that is gone. A scheduled
task every minute but that may not be fast enough.

Ryan Thompson
James Tower Media Design 
Websites, Multimedia, Videos, Catalogs, e-Catalogs and more.
http://www.jtmd.com
mailto:[EMAIL PROTECTED]

--
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Re: Any good way to maintain server variables?

[Reuben King]

In <4EC96B864C1CD211BBC500805FE6FDBC02B48B9E@TCEXCH1>, Thompson, Ryan K 
(James Tower) ([EMAIL PROTECTED]) in a fit of unbridled passion, 
wrote:
> We are implementing a clustering solution that can do sticky session but it
> needs a unique value 
> it either a cookie variable or URL variable per server. Rather that changing
> the code on each server I'd like to use 
> a variable that would be unique on each server. Does anyone know of a good
> way to set and maintain a 
> server or cgi variable to do this?

Fine, so create a unique cookie for each server and have a many-to-many 
setup in your database reconciling those unique keys to whatever session 
settings you'd like to store.  I suggest you make your unique server 
cookies very unique and not just an incrementing serial number.

> The domain name will not change in the HTTP header so we can't use that. I
> thought of putting a browser in the startup 
> of each server to hit a page but when CF restarts that is gone. A scheduled
> task every minute but that may not be fast enough.

You can't create a unique cookie name for each server?  What about a 
single cookie that stores each of the server's unique keys in a text 
block that is parsed out by each server programmatically?  

> 
> Ryan Thompson
> James Tower Media Design 
> Websites, Multimedia, Videos, Catalogs, e-Catalogs and more.
> http://www.jtmd.com
> mailto:[EMAIL PROTECTED]
> 
> --
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit 
>http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
>message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
> 
r
--
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.

Re: Any good way to maintain server variables?

[Al Musella, DPM]

You could also just test in the application.cfm.. if the server 
variables are not defined, make one up!  If you rely on a scheduled task, 
there will always be a chance that a page could execute before the variable 
is declared and trigger an error.
Al



>he domain name will not change in the HTTP header so we can't use that. I
>thought of putting a browser in the startup
>of each server to hit a page but when CF restarts that is gone. A scheduled
>task every minute but that may not be fast enough.


--
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.