If you planning on using a single DB server for the forseeable future or even just have a lower spec box one dealing entirely with sessions.
Table like session_id (have used the apache session cookie in the past) user_id timestamp No need for a primary key and you can pass the data back to as many coldfusion servers as you need to. HTH. Olly. >So the question is, what must be taken into consideration thinking this >far ahead? Things like sessions -- we can't use the standard session >scope because this won't work across load-balanced sites (unless each >initial request gets allocated to a certain box and all future requests >go to the same box, but we don't want this constraint). >Are there any suggestions for using user sessions across (possibly) >load-shared boxes? Yes we could leave it up to the load-balancer >(sticky sessions etc) but I'd rather have the control myself and make >it part of the application functionality. -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
