> The client would dearly love to break its dependence on Akami > caching, and it now looks like we may be able to do so. Thanks > everyone for your help in this.
Just as a side note, I believe Akami does geographic cache controlling in addition to simply caching out of a central location (as do several other big names in the caching business). This means that users in, say, China, hit the cache controlling machines in China, rather than your central servers in, say, Atlanta. If all your users are fairly geographically centralized, this may not introduce noticeable problems. However, if your user-base is spread across the globe, a centralized solution out of a single data-center may introduce latency problems for more distant users. Some companies (salesforce.com, for example) have several data-centers, geographically dispersed so that customers end up hitting the closest one. Perhaps Akami has reports that can be generated from their usage to provide management with the data needed to decide whether users are clustered near your data-center (such as on the same continent), or if they're all around the world. I have no idea how to do something like this, other than assigning a server to a given user based on their setup profile. I'm sure there are some DNS tricks that can be used to resolve a user to a geographically designated server, but that sort of dark-art mojo is outside my bag of tricks. -tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
