I think we have to identify using ipaddress of the user. Take other inputs too.
ocjp 6 — Feeding a person with food is a great thing in this world. Feeding the same person by transferring the knowledge is far more better thing. The reason is the amount of satisfaction which we get through food is of only one minute or two. But the satisfaction which we can get through the knowledge is of life long.
Mohana Rao wrote:@Pual, here the problem is how to identify customer country. one case it may fail if we were identifying by ip address if end user was using proxy ip address.
Indeed you are. And my code asks why you are trying to solve that "problem". In case you didn't run it, it demonstrates that some parts of Canada (which you will find is a country) use decimal points and other parts use decimal commas. So why is that a "problem" worth considering at all?
Mohana Rao wrote:Thanks for reply Paul it's not my requirement i'm trying to help the guy who posted that question...
Notice that I didn't address you specifically when I posted that comment. Which was intended to point out that the requirement is, um, not a very good one. Which means that continuing to go on about useless things like IP addresses isn't worth anybody's time.
Actually, rereading the thread I see that you were the one who posted the idea about IP addresses. Which it now appears wasn't a very good idea because people on the same street in Canada, with the same ISP, could be using English and French. So not only does the country of the client provide the desired information, neither does the IP address of the client.
Paul, What i thought was using client ip address we can identify the country where the request is coming from so that we can enable that language format. Here i'm not worrying about what are languages are known by the end user.