|
|
Posted by Steve on 08/19/07 20:40
"axlq" <axlq@spamcop.net> wrote in message
news:faa5da$qs9$1@blue.rahul.net...
| In article <YgKxi.41$b23.10@newsfe12.lga>, Steve <no.one@example.com>
wrote:
| >here's a straight-forward method to begin with. any other issues raised
can
| >be answered easily with a little investigation and modification to this
| >general approach. the best you can do is find the issuing isp. most of
the
| >time, the user of the ip is very near the issuer.
|
| [snip example to get country information from whois server like ARIN]
|
| That's an interesting approach, but seems impractical to me. Most
| whois servers will cut you off if you have too many requests in one
| day. For a high-traffic site that needs geolocation information, a
| local database may be best.
really? the job of a name server is to be queried. do you have info on the
'cut off' that 'most' ns servers use? i'm not saying a local db isn't a good
idea, however see that you've avoided anything in doing so. you may well be
able to pull out geo info from your db, but nothing's to say your local db
isn't out of sync with actual ns server data. there's a whole bunch of
background coordination you'd have to do in order to make sure you were in
sync. to me, that seems more impracticle than just going to the source...at
least until you justify your claim of 'cut off' and 'most'.
;^)
Navigation:
[Reply to this message]
|