Josh, Your belief might not be correct, although it can depend on what content you are serving, how that CDN is set up, and how your sessions are set up.
If a session is established on Server A, then activities on Server B generally won't impact Server A. If you are only serving cached content or images on Server B, then I doubt Server B benefits from session variables at all. Even with domain cookies set, activities on Server B won't prolong the Server A session since the session is maintained on the server, not in the cookie. Setting domain cookies would potentially be a mistake, since you would be adding overhead with no benefit. If a.site.com has all your dynamic content and sessions while b.site.com has all your images, the Web browser can not only load the site faster because this gets around the HTTP simultaneous connection limits, but it is also faster because you don't have to send pointless cookie information to b.site.com with every image request. So for many people looking to optimize network traffic, the goal is to avoid sending cookies to all the servers. The main uncertainty is what type of CDN you are using. Most often these are used to help deliver static Web content or files, as opposed to dynamic Web site content. I would expect that your CDN provider has a FAQ or technical guide that discusses how to handle session variables if you are serving dynamic content. That is where I would look for this information. For your second question, I would assume the answer is "no," but I would certainly test this if it is a concern for you. -Mike Chabot On Wed, Aug 6, 2008 at 3:07 PM, Josh Nathanson <[EMAIL PROTECTED]> wrote: > Hello, > > We are set to start using a Content Delivery Network shortly. For those not > familiar, the idea is that when someone requests www.mysite.com, the CDN > intercepts that request, and either sends back cached content if it has it, > or goes to origin.mysite.com to retrieve fresh content. > > Because of this, I believe I need to set setDomainCookies=true in > Application.cfc so that the sessions are maintained whether the request is > from origin.mysite.com or www.mysite.com. > > 1) Is this correct? I mean when the CDN sends the request to > origin.mysite.com for fresh content, CF will try to set cookies for > origin.mysite.com, yes? > > 2) If I do this change to setDomainCookies=true, will it kill all the > current sessions on the server? > > -- Josh ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:310308 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
