![]() |
Client and server processes can execute in geographical locations having different time zones. To date, all internationalization literature and resources have concentrated mainly on code set and locale related issues. They have mostly ignored the time zone issue, even though business methods can be sensitive to time zone as well as to locele.
For example, consider a simple eCommerce application for buying, selling, or trading stocks based on requests originating from its subscribers. Assume that the server is placed in Wall Street in a computer configured for the Eastern Standard Time (EST) time zone. Depending on market volatility, the result of a stock purchase request originating from a Central Standard Time (CST) client can vary dramatically if the eCommerce application does not account for the time zone differential between client and server.
Other time zone sensitive operations include time stamping messages logged to a server and resource (file, database) accesses. The concept of Daylight Savings Time (DST) further complicates the time zone issue. Neither the CORBA nor the J2EE specifications address the issues adequately and traditional methods of solving the problem are limited.
Related concepts... | |
Computers with differing endian architectures or code sets | |
Computers located in different locales | |
View PDF file... | |
To view a PDF file containing this article and related articles, click: | |
![]() | |