![]() |
Client and server processes can execute in geographical locations having different time zones. For example, a Spanish client may invoke a business method upon an object residing on an American server. Some business methods can be locale sensitive in nature; for example, given a business method that returns a sorted list of strings, the Spanish client will expect that list to be sorted according to the Spanish collating sequence, not in the server's English collating sequence. Since data retrieval and sorting procedures run on the server, the locale of the client must be available in order to perform a legitimate sort.
A similar consideration applies in the instances where the server has to return strings containing date, time or currency, exception messages, and so on, formatted according to the client's cultural expectations. Neither the CORBA nor the J2EE specifications have architecturally addressed the locale mismatch problem, and other options involving extra parameters are not practical or have limitations. For example, requiring an extra parameter could require interface changes, which is a serious concern for deployed applications.
Related concepts... | |
Computers with differing endian architectures or code sets | |
Computers located in different time zones | |
View PDF file... | |
To view a PDF file containing this article and related articles, click: | |
![]() | |