RE: [registrars] Bounced message from Gandi
no offence buddy :) - your scripts are awesome ( i still use them) - to be
more specific than what i wrote below -
1. Perl by default is obfuscated (for most people anyways) :)
2. perl runs as a cgi process and is not callable within a java program with
as for separating out information - it is quite easy to write regex for some
of the stuff such as -
* email addresses
Other aspects like postal codes etc are complex but can be treated as units
(ie complete address block with zipcode) - though i have noticed with some
registrars it is difficult to separate out between the addresses and phone
numbers, however i am sure each registrar can do this for their own whois
format, since they would know their own output better than we would
the worst are those registrars who merge contact information of admin, tech,
billing etc into ONE lump of information if they are the same. Those are the
worst for parsing
Tel: 91-22-6370256 (4 lines)
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:email@example.com]On
> Behalf Of Michael D. Palage
> Sent: Monday, January 21, 2002 9:54 PM
> To: firstname.lastname@example.org
> Subject: [registrars] Bounced message from Gandi
> On Sun, Jan 20, 2002 at 12:48:17PM +0530, Bhavin Turakhia took time to
> > > I think Gandi published their perl whois Extractor see
> > > http://open.gandi.net/
> > it is an awesome effort and commend them for it - but there are issues -
> > 1. perl makes it difficult to be integrated in a registrars code (we use
> > in our first version of our api and it is a pain - socket 80 connection
> > blah)
> No it does not. At least for Perl-based Registrar ;-)
> > 2. the code is not too readable and modifiable ... (not
> perfectly modular)
> Why not readable ?
> It is easily modifiable, and it is truely modular I think.
> (patches were already done from people outside)
> If not do not hesitate to tell me why it is not !
> > 3. does not separate out various contacts.
> This is true... but false in my development version I will put out
> someday ;-)
> Do not forget why we needed it : for transfers, and we sent an email
> to all contacts. We do not need anything else (besides owner data).
> But, it is open, anyone is welcome to modify it.
> > we are working out a language definition to define java properties files
> > which will parse any registrars whois and split the data into whatever
> > information you need gleaned.
> I doubt this is really possible if to be done completely.
> Think about postal adresses and zip code for example.