Re: Net::Whois::RIPE

2003-05-30 Thread Roger Burton West
On Thu, May 29, 2003 at 10:44:11AM -0300, Luis Campos de Carvalho wrote:
Dirk Koopman wrote:
jwhois?
  Oh, man...
  I think you mentioned a *Java* program...

$ file $(which jwhois)
/usr/bin/jwhois: setgid ELF 32-bit LSB executable, Intel 80386, version
1 (SYSV), dynamically linked (uses shared libs), stripped

Debian Depends: libc6 (= 2.2.4-4), libgdbmg1, adduser, dpkg (= 1.9.0)

I see no Java here.



Re: Someone must have solved this one ?

2003-05-30 Thread Toby Corkindale
On Tue, May 27, 2003 at 07:44:58PM +0100, Nik Butler wrote:
 Heres a problem for the perl ancients among you.
 
 One of our customers ( I say our since like the Borg, ive joined a
 collective ) requires a regular deduplication of list information (
 mostly CSV ) against a existing database (SQL Server 2k) .
 
 now im fairly sure that this is exactly what Perl was designed for ...
 however when searching for tools and advice on utilising those tools I
 do tend to come up a little non plussed.
 
 has anyone actually had experience ( postive or negative ) with such
 tools in doing mail address deduplication of text files with SQL 
 

The laziest method would be to let the SQL server do the work.. eg:
CREATE UNIQUE INDEX address_idx ON contacts (sirname, house_number, postcode);

However, before you could use this you would have to normalise all your
information. For eg: Make sure the postcode was in uppercase with a space
seperator. Not hard to do though; it's a once-off for the SQL database, but
you'd need to run it on every entry from the new text files. Not a big loss
though.

I know this is barely using Perl as anything other than an intelligent DB
frontend, but you have to admit databases are quite good at doing indexing and
so forth - so why try to re-write the wheel?

tjc

Note: Example above is taken from PostgreSQL, so may not work verbatim on
inferior DBs ;)




Re: [ANNOUNCE] Tim O'Reilly in London

2003-05-30 Thread Toby Corkindale
On Wed, May 28, 2003 at 10:27:57AM +0100, Mark Fowler wrote:
Er, isn't the 'M' in there something to do with , cough, MySQL ... ?
   Sh. The 'P' is PHP.
  Or python.
 Or Perl.  Or it seems these days, getting back to John's point, Postgres.
 
 I seem to be running FASP these days for ickle applications (FreeBSD,
 Apache, SQLite and Perl.)  These acronyms are all very silly.

That would make me a LAPP dog. (But I used to be a UIIC monkey.)

tjc

((DEC) UNIX, ISDN, Informix, C)




Re: Net::Whois::RIPE

2003-05-30 Thread Lusercop
On Thu, May 29, 2003 at 01:42:37PM +0100, Mark Morgan wrote:
 On Thu, 29 May 2003, Lusercop wrote:
  Can't you just ask OpenSRS for the information? that's what we do.
 Because OpenSRS is my employer. :)  The minimal parsing that we need to do
 is just to get the admin email address for transfers, but even doing that
 changes on an all-to-regular basis for many registrars.

Whoops, self-LART. ISWYM, then. Can I rant at you about repeatable testing,
then, or has Chris already made himself enough of a pain with this?

-- 
Lusercop.net - LARTing Lusers everywhere since 2002



Re: Net::Whois::RIPE

2003-05-30 Thread Dirk Koopman
Nope.

jwhois is a standard 'gnu' program written in C

Dirk

On Thu, 2003-05-29 at 14:44, Luis Campos de Carvalho wrote:
 Dirk Koopman wrote:
  jwhois?
 
Oh, man...
I think you mentioned a *Java* program...
 
/me washes his mouth with soap
 
Please don't suggest a perl programmer to use Java... =-]
[]'Z!
 

-- 
Please Note: Some Quantum Physics Theories Suggest That When the
Consumer Is Not Directly Observing This Product, It May Cease to
Exist or Will Exist Only in a Vague and Undetermined State.





Re: Net::Whois::RIPE

2003-05-30 Thread Lusercop
On Thu, May 29, 2003 at 10:38:06AM +0100, Chris Andrews wrote:
 On Thu, May 29, 2003 at 10:26:54AM +0100, Lusercop wrote:
  Can't you just ask OpenSRS for the information? that's what we do.
 If you're transferring from another registrar, you have to parse
 *their* information in order to feed it to OpenSRS. 

As you well know, I rely on the user to get that bit correct. :-)

-- 
Lusercop.net - LARTing Lusers everywhere since 2002



Re: weird eval

2003-05-30 Thread Patrick Mulvany
On Wed, May 28, 2003 at 05:41:49PM +0100, Ben wrote:
 What circumstances are there under which eval {}; will not trap a program exit ?
 
 I assume a naughty XS module segfaulting will do for it - but are there any
 others?

The XS module may not directly segfault but rather leave garbage around that causes 
segfaults when they are cleared up.

perl -e 'eval {use Clone qw(clone); $a={}; undef $a; $c=clone $a;print cloned\n;}'

clone does not directly appear to cause the segfault but the clean up of $c going out 
of scope causes the segfault.

see :- http://rt.cpan.org/NoAuth/Bug.html?id=2252 for a fuller explaination.

Hope that helped some

Paddy 



Re: [ANNOUNCE] Tim O'Reilly in London

2003-05-30 Thread Jonathan Stowe
On 29 May 2003, Randal L. Schwartz wrote:

 OpenBSD, PostgreSQL, Perl = I'm down with OPP (yeah, you know me!)


I think Open Source Operating System, Open Source Database Manager,
Open Source Programming Language ( or OOO ) is more the thing these
days ;-)

/J\




Re: [ANNOUNCE] Tim O'Reilly in London

2003-05-30 Thread Lusercop
On Fri, May 30, 2003 at 12:32:24AM +0100, Jonathan Stowe wrote:
 On 29 May 2003, Randal L. Schwartz wrote:
  OpenBSD, PostgreSQL, Perl = I'm down with OPP (yeah, you know me!)
 I think Open Source Operating System, Open Source Database Manager,
 Open Source Programming Language ( or OOO ) is more the thing these
 days ;-)

For some reason, the idea of Olfactory Object Orientation came to me
just now.

Yeah, your object model smells.

-- 
Lusercop.net - LARTing Lusers everywhere since 2002



Re: URL wierdness...

2003-05-30 Thread Andy Williams \(IMAP HILLWAY\)

- Original Message - 
From: Roger Burton West [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Friday, May 30, 2003 9:24 AM
Subject: Re: URL wierdness...


 On Fri, May 30, 2003 at 09:16:25AM +0100, Andy Williams (IMAP HILLWAY)
wrote:

 Now... this works fine for almost every URL I can think of apart from 2:
 http://www.acxiom.co.uk  http://www.acxiom.com
 These 2 both return 500 Internal Server Error but work fine if you go
to
 them with a browser!

 Not with my browser (Dillo/0.7.1).

 Doesn't work even if I fake the user-agent to be IE5.

 Oh, what a surprise, they're running IIS.


Yes they are. but I don't have any trouble getting to other IIS sites!

This is very strange!

Andy




Re: URL wierdness...

2003-05-30 Thread Jonathan Stowe
On Fri, 30 May 2003, Roger Burton West wrote:

 On Fri, May 30, 2003 at 09:16:25AM +0100, Andy Williams (IMAP HILLWAY) wrote:

 Now... this works fine for almost every URL I can think of apart from 2:
 http://www.acxiom.co.uk  http://www.acxiom.com
 These 2 both return 500 Internal Server Error but work fine if you go to
 them with a browser!

 Not with my browser (Dillo/0.7.1).

 Doesn't work even if I fake the user-agent to be IE5.

 Oh, what a surprise, they're running IIS.


And worse ASP.Net, although the error is not directly to do with
approaching an ASP.Net as I have tested this with one of my own which
works fine (even with GET /PaymentReport/ HTTP/1,1^H ;-)  - I would
imagine they are doing something bad and evil with the
System.Web.HttpRequest and not catching the exception when something they
expect to be an object is actually null.

/J\




Re: Someone must have solved this one ?

2003-05-30 Thread Jon Reades
Nik Butler wrote:
snip
has anyone actually had experience ( postive or negative ) with such
tools in doing mail address deduplication of text files with SQL 
snip

I doubt that there are many drop-in tools out there since the question 
of what constitutes a duplicate address/customer will depend on the 
nature of the business.

For instance, if you're BG then the chances that you have two customers, 
one named Jon Reades and the other named John Reades at the same address 
and postcode are very low. If you're a bookstore then the chances are 
rather higher.

I've heard of some interesting ways of tackling the problem that 
generally involve attempting to correct for common input errors by 
hashing the name in one or more of the following ways for the purposes 
of comparing two records that you have reason to believe might be the 
same person:

1. Removing all duplicate vowels (so 'aa' becomes 'a', and so on)
2. Remove all duplicate consonants (so 'll' becomes 'l', and so on)
3. Removing vowels, whether single or multiple, altogether and replacing 
with a single placeholder (s|[aeiow]+|-|g)
4. Lower-casing everything
5. You might apply some similar rules (very carefully) to some types of 
address/postcode information
6. You might also consider trying variations on commonly mis-heard 
letters -- D, E, G, P, etc.

But basically, the rules are up to you in terms of what you'll accept as 
the tradeoff between verification and deduplication.

HTH,

jon
--
jon reades
fulcrum analytics
t: 0870.366.9338
m: 0797.698.7392
f: 0870.888.8880
lower ground floor
2 sheraton street
london w1f 8bh