Speaking as someone who's work routes their internet traffic through a gateway in Phoenix, AZ despite being based in Australia, guessing time zones based off IP location is a lot more prone to error than detecting it based off the client.
On 31 July 2014 17:54, Stephen Chrzanowski <pontia...@gmail.com> wrote: > Looking back at the clarification of what the OP wanted to do, I've got > this to recommend; > > If your users are talking to your server via the internet and not via a VPN > connection, instead of relying on what time zone your users browser is > giving you, look at what IP they're calling in from and do an IP to > geographical look up to find out where they are. From there you'd be able > to catalog a 'best time of contact' based on what the Geolocation service > gives you. > > Doing a quick google search on "ip to geo" I found these two: > http://www.iplocation.net/ and http://www.geoiptool.com/ > > By the looks of it, for a modest yearly fee, you'd be able to download a > database of IPs to locations and you'd be able to get time zone information > right from there. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
