On 3/21/06, Dave Watts <[EMAIL PROTECTED]> wrote: > If you use round-robin DNS, it is unlikely that the user will be sent to one > server, then another. When the user attempts to connect initially, the DNS > server will issue one IP address, and that IP address will be cached for > some time by the client. Even if that first server fails, the user will not > be sent to another server.
Most probably we'll be using a very low TTL, so there is a chance that an user will hit jump from a server to another: even if most browsers just cache the IP address and ignore the TTL, that may be not true for all. > Aside from that, though, I don't think there's any way to share CFLOGIN data > without associating it with the Session scope, and sharing that across the > servers. This would require CF clustering. When you use the CFLOGIN tag, it > does write a cookie which contains something, but I don't know if it > contains everything that is set by CFLOGINUSER. That's exactly what I'm wondering: does the cflogin cookie include all the info (username/password) needed to (automatically) (re)authenticate the user on a server if he previously authenticated on another server? Anyone tried this? Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:235907 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
