[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

whois server features

Subject: whois server features
From: nick at foobar.org (Nick Hilliard)
Date: Wed, 07 Jan 2015 20:48:22 +0000
In-reply-to: <[email protected]>
References: <CAH_OBidrQiAP++Tjuz_4goKMcSxo+yJ4fMyR=jpAYSY0+F96_w@mail.gmail.com> <CAH_OBie503gHHjDrBM_Jdwj1fNVOJSL6DEGQe3zxBxMHVv8vnQ@mail.gmail.com> <[email protected]> <CAH_OBicKFtrSCzTUZHU_Z5oP8kEpELoH+64ouwvr-Df1jqFRhg@mail.gmail.com> <[email protected]>

On 07/01/2015 20:07, Bill Woodcock wrote:
> Correct.  It gets you a blob of text.  Sometimes, a blob is just a blob.
> Other times, it contains what _appear_ to be key-value pairs, but are
> instead loosely-formatted text.  Other times, it contains
> textually-represented key-value pairs that are programmatically
> generated from an actual database, and can thus be re-imported into
> another database.  Depends whatâ??s on the back end.

If only we could create a committee to fix whois...

Nick

Follow-Ups:
- whois server features
  - From: joelja at bogus.com (joel jaeggli)
- whois server features
  - From: johnl at iecc.com (John Levine)

References:
- Fwd: whois server features
  - From: ag4ve.us at gmail.com (shawn wilson)
- whois server features
  - From: woody at pch.net (Bill Woodcock)
- whois server features
  - From: ag4ve.us at gmail.com (shawn wilson)
- whois server features
  - From: woody at pch.net (Bill Woodcock)

Prev by Date: whois server features
Next by Date: whois server features
Previous by thread: whois server features
Next by thread: whois server features
Index(es):
- Date
- Thread