Commits on Sep 28, 2009
  1. Release Whois 0.8.0

    weppos committed Sep 28, 2009
Commits on Sep 27, 2009
Commits on Sep 25, 2009
  1. Improved code coverage.

    weppos committed Sep 25, 2009
  2. Improved documentation.

    weppos committed Sep 25, 2009
Commits on Sep 24, 2009
  1. Completed multi-part answer parsing with multiple parsers, blank pars…

    weppos committed Sep 24, 2009
    …er and parser selection based on registered methods.
Commits on Sep 23, 2009
  1. Improved previous commit. Instead of raising an exception when #parse…

    weppos committed Sep 23, 2009
    …rs is called, raise only when a parser is internally required.
  2. Refactoring Answer#parser. Now instead of a single parser, Answer#par…

    weppos committed Sep 23, 2009
    …ser returns an instance of Answer::Parser.
    Answer::Parser is basically a proxy class: it holds a parser for any answer part and (in the future) is supposed to negotiate parser responses forwarding each method call to the right parser.
  3. Answer now accepts an array of Whois::Answer::Part instead of a less …

    weppos committed Sep 23, 2009
    …readable array of array.
Commits on Sep 20, 2009
  1. Use whois server host instead of extension because some server suppor…

    weppos committed Sep 20, 2009
    …ts multiple top level domains.
  2. Added (.com, .net, ... TLDs) parser. The parser is n…

    weppos committed Sep 20, 2009
    …ot intended to be finished yet. In fact, the system still need to be improved in order to support thin servers ( is a thin server).
    Also, I don't like very much the internal Scanner. Probably it's going to be replaced or improved in a future version.
  3. Documented main Whois file.

    weppos committed Sep 20, 2009
  4. Whois::Answer#i_am_feeling_lucky (formerly Whois::Answer#i_am_feeling…

    weppos committed Sep 20, 2009
    …_lucky) become obsolete since the introduction of Answer parsers.
  5. Renamed Whois::Response to Whois::Answer. This change is required to …

    weppos committed Sep 20, 2009
    …avoid confusion between query-answer and server request-response. A Whois::Answer is composed by one or more parts, corresponding to single server answers.
  6. Added support for multipart answers. This is useful in case of thin s…

    weppos committed Sep 20, 2009
    …ervers such as .com or .net because the parser needs to know all different responses in order to load all single scanners.
Commits on Sep 18, 2009
  1. Release Whois 0.5.3

    weppos committed Sep 18, 2009
  2. In some rare circumstances the server guessing fails to return the ri…

    weppos committed Sep 18, 2009
    …ght server but returns an other server instead (closes #260).
Commits on Sep 15, 2009
  1. extracted all scanners into separated classes in order to make easier…

    weppos committed Sep 15, 2009
    … extract shared features.
  2. Added a (.de) parser

    f0086 authored and weppos committed Sep 3, 2009
    Signed-off-by: Simone Carletti <>
Commits on Aug 26, 2009
Commits on Aug 24, 2009
  1. Release Whois 0.6.0

    weppos committed Aug 24, 2009
Commits on Aug 23, 2009
  1. Defined the most part of parser response methods and objects.

    weppos committed Aug 23, 2009
    Finalized the WhoisNicIt parser.  It should serve as example of how to create a server parser.
  2. Refactoring the Response parser.

    weppos committed Aug 23, 2009
    Instead of using a Regex based parser, only scan the response once using a StringScanner then query the "Abstract Syntax Tree" to get nodes and values.
Commits on Aug 20, 2009
  1. Release Whois 0.5.2

    weppos committed Aug 20, 2009