I agree. Is there a cogent reason why so much stuff is under Apache? Apache doesn't seem like a proper category. WWW might be better for web-specific stuff, but for this, it seems like geo is the clear module directory it should be in:
http://www.cpan.org/modules/by-module/Geo/ Does Apache-GeoIP require Apache software? Is there a module to abstract Apache modules such that apache wouldn't have to be installed to get all that apache:: stuff to run? It would be something like DBI for databases where the equivalent of DBD would be the actual web server software (Apache). -----Original Message----- From: darren chamberlain [mailto:dlc@;users.sourceforge.net] Sent: Friday, October 25, 2002 11:09 AM To: [EMAIL PROTECTED] Subject: Re: [RFC] Apache-GeoIP module * Randy Kobes <[EMAIL PROTECTED]> [2002-10-17 17:01]: > I've placed at > ftp://theoryx5.uwinnipeg.ca/pub/other/Apache-GeoIP-0.26.tar.gz > a package providing a mod_perl interface to the GeoIP library, > which is used to look up in a database the country of origin of > an IP address. See http://www.maxmind.com/ for details. Out of curiousity, why is your package limited to Apache? I've looked at the code a bit, and don't see why the GeoIP stuff needs to be attached to Apache. I'd like to see, in addition to the Apache stuff, a generic GeoIP library that can be used from outside Apache, like in log-eating scripts. Sorry for picking up this thread this so late; I'm a little slow. ;) (darren) -- Millions long for immortality who do not know what to do with themselves on a rainy Sunday afternoon. -- Susan Ertz
