Re: Detecting timezone for client browser
From: Kevin Spencer (kevin_at_takempis.com)
Date: 03/19/04
- Next message: george d lake: "Setting things to nothing ?"
- Previous message: bradbury9: "Error code 128"
- In reply to: Bryan Donaldson: "Re: Detecting timezone for client browser"
- Next in thread: NWx: "Re: Detecting timezone for client browser"
- Reply: NWx: "Re: Detecting timezone for client browser"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 19 Mar 2004 13:02:36 -0500
Good point. A much harder alternative would be to do a WHOIS lookup on the
IP address of the client computer, and see what (if any) LatLong and/or
address data is registered for the IP or the Network that owns the IP.
-- HTH, Kevin Spencer .Net Developer Microsoft MVP Big things are made up of lots of little things. "Bryan Donaldson" <bryandonaldsonREMOVETHIS@REMOVETHISmindspring.com> wrote in message news:eItf3jdDEHA.4076@TK2MSFTNGP10.phx.gbl... > Note that this solution assumes (as you must) that the time on the PC is set > correctly. But you should warn the user that you're making that assumption. > > > "Kevin Spencer" <kevin@takempis.com> wrote in message > news:emkI$jbDEHA.3016@TK2MSFTNGP11.phx.gbl... > > On your server, you should know the UTC (GMT) time. On the client, the > > browser knows what the local time is. If you have some JavaScript on the > > client that populates a hidden form field with the current (client) date > and > > time, when it posts back to the server, it's a relatively simple meatter > of > > DateTime arithmeetic to determine the difference in the time, which is > what > > you really need, rather than the time zone. > > > >
- Next message: george d lake: "Setting things to nothing ?"
- Previous message: bradbury9: "Error code 128"
- In reply to: Bryan Donaldson: "Re: Detecting timezone for client browser"
- Next in thread: NWx: "Re: Detecting timezone for client browser"
- Reply: NWx: "Re: Detecting timezone for client browser"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|