> I'm not so sure. It depends on the use case, IMHO.
+1
If the OP only needs the *country* identified, GeoIP on the server is
the easiest solution.
For any finer granularity, GeoIP (or any IP-based system) is not very
reliable. (At the moment I'm in a moving vehicle south of Pismo Beach
California, and GeoIP thinks I'm in Manteca -- *way* off.)
But the client-side solutions are still a work in progress too, AFAICT :-)
FWIW,
--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
twitter: @hassan
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
No comments:
Post a Comment