Internationalization of web services is an emerging field.
The is a draft specification WS-i18n (short for WS-internationalization)
that drafts specifications for passing locale, language, and formatting
information from a client to a web service.
If you're simply looking to return fault text, or response text in specific
languages, I believe the suggested practice is to push locale preferences
into the extensible SOAP headers. Keeping the method interfaces free of
locale information.
If you're using ASP.NET you can then extract that, creating a CultureInfo
object from that locale to pass to
System.Threading.Thread.CurrentThread.CurrentUICul ture. That way, if you
have localized text that you have stored in your resources the resource
manager will automatically handle getting the appropriate text, defaulting to
a neutral culture for that locale or defaulting to an invariant language.
--
Browse
http://connect.microsoft.com/VisualStudio/feedback/ and vote.
http://www.peterRitchie.com/blog/
Microsoft MVP, Visual Developer - Visual C#
"Paweł Piotrowski" wrote:
Hi!
What are the best practises when building WebService
supporting multilanguage users?
For example, when WebService checks some business rules
and returns message to the user.
Best regards
Pawel