Hello *,
David.Kessens@ripe.net writes: My personal opinion is that such a 'best guess' method is just fine:
I do not agree on this one. If more than one key value is given only objects matching all keys should be returned. That is the behaviour I would expect. If the user wants to loosen up the query, they can consciously do that. Since whois responses are fast, there is no point in second guessing the user's intentions to save time.
Daniel
I agreee with Daniel's opinion. We are using some scripts to check out whether a person is in the database or not. A "not found" message is the response I (and my scripts ;-) would expect 'cause the script can not decide if a "best guessed"-object is really the person in question. Perhaps, the best guess feature should be switched on only if desired !? Comments? rgds, Dirk Pantring (DE-NIC Hostmaster) -- _0_ Dirk Pantring eMail: pantring@nic.de / \ RZ<-- Rechenzentrum/DE-NIC \_______/ Universitaet Karlsruhe Tel: +49 721 373723 / / | \ \ Postfach 6980 Fax: +49 721 373741 _/_/__|__\_\_ D-76128 Karlsruhe Fax: +49 721 32550