Quote:
Originally Posted by NickPapageorgio
Pretty much, but broken down by U.S. City if possible. Probably with an if/else statement that'll say "Ok, if it's from the U.S. break it down by city {else} break it down by country". See what I mean?
|
I've looked at the city issue, and the problem is that the data becomes too bulky to be easily handled w/o a database, which adds undue complexity on one hand, and a lot of maintenance overhead - it's not too often that countries change ip ranges, but more so with towns.
Basically the entire idea of having a lightweight solution goes out the window, and the architecture changes - if you're going to have it in a db, might as well have one single db for everybody, cause it's easier to maintain, and just connect to that, etc.
So I'm affraid it will have to be just countries.