Uneko nire proiektua, erabiltzaile batzuk izango da mundu osoan zehar bidaiatzeko eta, helmuga hainbat iristean dute, 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, Izan ere,… Bat naiz Parking oraingoz).
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.
Bi ikuspegi ikertu goaz:
- HTTP Handler: A pertsonalizatu HTTP handler IIS instalatuta itxura izango duen erabiltzailearen profila MOSS, irudikatu gogoko hizkuntza, eta, ondoren, inguruan behar HTTP goiburua aldatzeko kontrol pasatuz MOSS aurretik.
- 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.
Zailtzen beste faktore 60k erabiltzaile laguntza behar dugu., buruz 1,000 aldi berean ahal izango dira karga gailurra MOSS sartzeko.
HTTP kudeatzailea badirudi nahiko zorrotzak, 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.
Mota ikuspegi norabidean global.asax leaning ari gara, batez ere, datuak cachean gordetzeko aukera gehiago izan dugu puntu horretan sinesten dugu.
Blogging gehiago dut gai honen inguruan gehiago ikasi dut gisa.
Honi buruz ezer ezagutzen baduzu dute, please post a comment 🙂
</amaiera>
Follow me on Twitter http://www.twitter.com/pagalvin
I have not tested this so I am not sure if it works.
The Page class has an InitializeCulture() method which can be overridden. If you do this in the code behind of your custom masterpage, you could do something along the lines of:
protected override void InitializeCulture()
{
// override virtual method InitializeCulture() to check if profile contains a user language setting
string UserCulture = GetCultureFromUserProfile();
bada ( UserCulture != "")
{
// there is a user language setting in the profile: switch to it
Thread.CurrentThread.CurrentUICulture = new CultureInfo(UserCulture);
Thread.CurrentThread.CurrentCulture = CultureInfo.CreateSpecificCulture(UserCulture);
}
}
Obviously you can build some caching into the implementation of this method.
Iturria: http://quickstarts.asp.net/QuickStartv20/util/srcview.aspx?path=~/aspnet/samples/localization/LocalizePers.src&file=LocalizePers_cs\LocalizePers_cs.aspx&lang=C# source
I’m thinking HTTP handler with the following flow:
1. Request comes in, check cookies for a session cookie for language preference (session cookies expire when the browser is closed)
2. Check if request is for ASPX page, if not, skip request
3. If cookie exists, set the language header to the value specified. You are done!
4. No cookie, take the authentication credential and look the user up in SPS, find language preference
5. Set cookie header and HTTP language header. Done.
First APX page request will have overhead of SPS lookup but every request from then on with have no lookups so will be native speed. No need for session cache or any other overhead by using a session cookie too. Once the browser is closed, the session cookie goes away. If the user changes their languages preference in SPS they just need to close and re-open the browser for it to take effect.
actually the http handler isn’t at the iis level…it’s at the application level (ISAPI Filters are at the IIS level)…i would be careful bc SP has its own handler…so be sure to test it out…i’ve done it before but have had some conflict with the SP handler.
I would be more inclined to use a HTTPHandler, arrazoi bakarra da, ez ditut gustuko SharePoint fitxategiak ukitu. Plus erraza da SharePoint irtenbide bat sortzeko HttHandler bat zabaldu ( eta erabili SPWebConfig API da web.config aldatzeko). Erabiltzaile karga duzu egin beharrik, Imajinatu sizable baserriko duzu nuke, ez benetan ez nahi modifiying fitxategiak joan zerbitzari bakoitzean.
Global.asa fitxategia hedatzeko konponbide baten bidez, ideia txarra da, atzera baduzu, Zure jatorrizko fitxategia pasatu da …
Abilezia ere konponbidea atzera botatzeko beharrik azkar ideia ona izan daiteke, kasu horretan, gauzak okertuko kudeatzailea de perf batera.