>>>Would I have to force session on a single server or could I build a
database fast enough to handle centralized session variables?
You could create one server just for session management or you can do it in
the database. The real issue here is just how much session data is there
and how frequently does it change? If it doesn't change significantly,
creating a uuid cookie and then call the database when you need the data is
the easy way to go. If the changes are extensive and frequent, this either
needs to be a very fast system, or consider caching some of it in RAM or
using a COM or EJB object to handle this instead of the database itself.
Also, since this sounds like a very data-intensive environment, put two NICs
in every web server and have two switches. One switch has the Internet side
and goes to a NIC on each server. This is how the outside world sees you.
The second NIC goes to the second switch which has the SQL servers attached.
This way it's a private "data network". Segmenting your traffic this way
isn't very expensive, but keeps the traffic isolated (security) and improves
the performance because IIS an have one NIC and CF/ODBC can have the other.
It's a way of adding more "threading or channels" to your environment.
--Doug
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
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.
