On my current project, some of the users will travel around the world and when they arrive at different destinations, use whatever machine is handy at the time. Those guest machines will be running Windows and installed and configured for the local locale. (I’ve just realized that the guest machines may not have the right language packs… probably won’t, in fact… I’m parking that one for now).
SharePoint needs to provide a mechanism whereby the user can pick their preferred language and then have MOSS honor that language regardless of how the user accesses MOSS. In other words, disregard whatever the browser tells IIS/MOSS and instead look up that preferred language and use it.
We’re going to investigate two approaches:
- HTTP Handler: A custom HTTP handler installed on IIS will look up the user’s MOSS profile, figure out the preferred language and then switch the HTTP header around as needed before passing control to MOSS.
- global.asax: Modify global.asax to do the same thing. We may modify something else, but the idea is that we find some place where we can insert our locale-switching logic.
The other complicating factor is that we need to support 60k users, about 1,000 of which may be simultaneously accessing MOSS at peak load.
The HTTP handler seems pretty drastic, but possibly the best place to put the code since it’s at the IIS level and all-knowing. It’s a good single point of work.
We’re leaning toward a global.asax type approach, mainly because we believe we’ll have more options for caching data at that point.
I’ll be blogging more on this subject as I learn more.
If you have know anything about this, please post a comment 🙂
Subscribe to my blog.
Follow me on Twitter at http://www.twitter.com/pagalvin