.co.za support - Ruby Whois

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion .co.za support
Received-SPF: pass (google.com: domain of wep...@gmail.com designates 209.85.220.174 as permitted sender) client-ip=209.85.220.174;
MIME-Version: 1.0
Sender: wep...@gmail.com
In-Reply-To: <4FEC2A41.6090...@gmail.com>
References: <3b997ab7-ef39-43ba-8487-6532d37d37cc@googlegroups.com>
 <f0f3400e-8edb-4d69-b904-b2bfa5099aba@googlegroups.com> <CAHNnY4ZWMFc1f8M6x4d6Q_+daYdivPoQ5hQv2tvQkzPLKqR...@mail.gmail.com>
 <4FE8A1B7.8060...@gmail.com> <CAAdVROkjEfFmi6uY3cMxpxuf-xoFFnSb4Y6SCfYEG3-Y+KG...@mail.gmail.com>
 <CAHNnY4Zq73QJfXjH68tXZuocEjMwRPL_=PGY3mT5Yn7fox2...@mail.gmail.com>
 <CAAdVROmLzSxBpkJEqKEQiNhoQvW9huqQyEa5G-uZxxWFfGU...@mail.gmail.com>
 <4FEA03C5.7000...@gmail.com> <CAHNnY4ZOFA74dZ1+b1fpfrXiwJEQNC5RGgvLE0=GmVMPvfX...@mail.gmail.com>
 <CAAdVROkr206F4ckhJo6vs=LhjYN82Nj7OgRCFa4R5SZZhYb...@mail.gmail.com> <4FEC2A41.6090...@gmail.com>
From: Simone Carletti <wep...@weppos.net>
Date: Thu, 28 Jun 2012 14:03:35 +0200
Message-ID: <CAAdVRO=fFEBu_vACkLD+3_ivEHTdQ=CUmQr0XBV2gYKxpob...@mail.gmail.com>
Subject: Re: .co.za support
To: ruby-whois@googlegroups.com
Content-Type: multipart/alternative; boundary=f46d0438958d1ee08704c3873360

--f46d0438958d1ee08704c3873360
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Jun 28, 2012 at 11:56 AM, Rory McKinley <rorymckin...@gmail.com>wrote:

> The bottom section (legacy output) has information such as admin and
> technical details which are not available through the new (EPP) whois
> interface (parts of section 2 in the output as well as sections 4 and 5 in
> their entirety). In an ideal world, I would transfer legacy domains to the
> EPP system and then the new whois output would be sufficient - but that is
> not an option.
>
> As far as I know, the data that is *not* provided by the new whois is
> still required to perform update/deletion operations through the legacy
> interface - and thus, I am stuck in a hole where I need to support both new
> and legacy whois :(
>

Here we are! Now it starts to make more sense. Thanks and sorry for the
long email exchange.

Speaking from a maintainer point of view, I would say that the output from
the new system would be enough to justify the change. There are parsers
with way less details of this.

However, I can feel your pain and your desire to have the full code merged
into the library. I'm just thinking whether it may be a good idea,
considering the fact that so far I decided to keep scraping and http
interactions outside the scope of this library.
I'm concerned because, once the code will be merged into master, it means
we'll have to officially support this.

I have a proposal for you, let me know what do you think.
Let's package everything into a plugin!

Here's my idea.

   1. We can update the current master of whois in order to use the output
   from whois.registry.net.za. In most cases, this is enough for the
   majority of users.
   2. The whois.coza.net.za parser will be removed and a new parser for
   whois.registry.net.za will be created to handle the standard response

That's it for the main whois library. But here it comes the whois-coza
plugin. This gem will provide all the features you described before:

   1. hook into .co.za definition in order to use a custom adapter
   2. the adapter will perform the request, check the response and extract
   the best response
   3. a new parser will be added to handle the HTTP response
   4. in case the response needs to be performed to the new interface, then
   the existing parser (bundled in the whois gem) will be used

Users whose want take advantage of this feature, will simply have to
require the whois gem + the whois-coza gem.

Does it work for you?


-- 
Simone Carletti
Application Developer

Site & Blog: http://www.simonecarletti.com/
LinkedIn: http://linkedin.com/in/weppos
Skype: weppos

--f46d0438958d1ee08704c3873360
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><div class=3D"gmail_quote">On Thu, Jun 28, 2012 at 11:56 AM, Rory McKin=
ley <span dir=3D"ltr">&lt;<a href=3D"mailto:rorymckin...@gmail.com" target=
=3D"_blank">rorymckin...@gmail.com</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">

<div bgcolor=3D"#FFFFFF" text=3D"#000000">The bottom section (legacy output=
) has information such as admin and
    technical details which are not available through the new (EPP)
    whois interface (parts of section 2 in the output as well as
    sections 4 and 5 in their entirety). In an ideal world, I would
    transfer legacy domains to the EPP system and then the new whois
    output would be sufficient - but that is not an option. <br>
    <br>
    As far as I know, the data that is *not* provided by the new whois
    is still required to perform update/deletion operations through the
    legacy interface - and thus, I am stuck in a hole where I need to
    support both new and legacy whois :(</div></blockquote></div><div><br><=
/div>Here we are! Now it starts to make more sense. Thanks and sorry for th=
e long email exchange.<div><br></div><div>Speaking from a maintainer point =
of view, I would say that the output from the new system would be enough to=
 justify the change. There are parsers with way less details of this.</div>

<div><br></div><div>However, I can feel your pain and your desire to have t=
he full code merged into the library. I&#39;m just thinking whether it may =
be a good idea, considering the fact that so far I decided to keep scraping=
 and http interactions outside the scope of this library.</div>

<div>I&#39;m concerned because, once the code will be merged into master, i=
t means we&#39;ll have to officially support this.</div><div><br></div><div=
>I have a proposal for you, let me know what do you think.</div><div>Let&#3=
9;s package everything into a plugin!</div>

<div><br></div><div>Here&#39;s my idea.</div><div><ol><li>We can update the=
 current master of whois in order to use the output from=A0<a href=3D"http:=
//whois.registry.net.za">whois.registry.net.za</a>. In most cases, this is =
enough for the majority of users.</li>

<li>The <a href=3D"http://whois.coza.net.za">whois.coza.net.za</a> parser w=
ill be removed and a new parser for=A0<a href=3D"http://whois.registry.net.=
za">whois.registry.net.za</a> will be created to handle the standard respon=
se</li>

</ol><div>That&#39;s it for the main whois library. But here it comes the w=
hois-coza plugin. This gem will provide all the features you described befo=
re:</div><div><ol><li>hook into .<a href=3D"http://co.za">co.za</a> definit=
ion in order to use a custom adapter</li>

<li>the adapter will perform the request, check the response and extract th=
e best response</li><li>a new parser will be added to handle the HTTP respo=
nse</li><li>in case the response needs to be performed to the new interface=
, then the existing parser (bundled in the whois gem) will be used</li>

</ol><div>Users whose want take advantage of this feature, will simply have=
 to require the whois gem + the whois-coza gem.</div><div><br></div><div>Do=
es it work for you?</div></div><br clear=3D"all"><div><br></div>-- <br><div=
>

<div>Simone Carletti</div><div>Application Developer</div><div><br></div><d=
iv>Site &amp; Blog: <a href=3D"http://www.simonecarletti.com/" target=3D"_b=
lank">http://www.simonecarletti.com/</a></div><div>LinkedIn: <a href=3D"htt=
p://linkedin.com/in/weppos" target=3D"_blank">http://linkedin.com/in/weppos=
</a></div>

<div>Skype: weppos</div></div><div><br></div><br>
</div>

--f46d0438958d1ee08704c3873360--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
