Since our apps deals with sports team schedules, timezones are
important for us. That's why I kept trying to suggest timezone support,
whenever you discussed locale support.
But your main question is how to determine a client's timezone. There
is no http-header way to get it, and a
I didn't use one, but I believe such service exists that resolves client
timezone by client IP.
Client IP - Location - TimeZone. And this all may be resolved in very
first request.
On Thu, Aug 19, 2010 at 10:43, Fernando Padilla f...@alum.mit.edu wrote:
Since our apps deals with sports team
In addition to my previous message:
http://stackoverflow.com/questions/41504/timezone-lookup-from-latitude-longitude
I will probably use this approach to determine initial client timezone since
I'm already use URL/IP to location functionality there:
Here's the service description:
http://www.geonames.org/export/web-services.html#timezone
http://www.geonames.org/export/web-services.html#timezoneAnd JSON example
for ping-service (XML is service also there):
http://ws.geonames.org/timezoneJSON?lat=37.41lng=-122.05
{time:2010-08-19
Yeah, i guess each his own. Though the ip resolution way does seem
cleaner in some ways, it does seem way more complicated in others..
and dependent on other services.. etc..
I guess we just realized that TimeZone Detector should be easily
pluggable, to fit people's taste and
One more thing, I've added Geonames to ping service to measure its
performance and got the following statistics:
Was made 47 requests (one for every 15 minutes) with average response time
750 ms.
During this period I got some bad responses:
{status:{message:the hourly limit of 3000 credits for
Hi,
I do everything server side with the help of a custom
TimeZoneAwareDatePicker wrapping your tapx datepicker. It takes a
source (I store everything in UTC) and display timezone (the users
timezone) to do the conversion. This suits me because I will almost
always know my users timezone as they
This is something that's been nagging me. Although there's a bunch of good
options for selecting a date (or date/time) as JavaScript components bult
into Tapestry, or available elsewhere ... none of them address the issue of
the client and the server operating in different time zones.
At the very
Hi
Just an add, related issue was reported there
https://issues.apache.org/jira/browse/TAP5-841
2010/8/7 Howard Lewis Ship hls...@gmail.com
This is something that's been nagging me. Although there's a bunch of good
options for selecting a date (or date/time) as JavaScript components bult
