[Developers] minor change in search api behavior (empty resultset will no longer be an error)

[Nicholas Paldino [.NET/C# MVP]]

I agree.

-1 

-----Original Message-----
From: developers-bounces at freebase.com
[mailto:developers-bounces at freebase.com] On Behalf Of Warren Harris
Sent: Friday, July 18, 2008 12:55 PM
To: For discussions about MQL,Freebase API and apps built on Freebase
Subject: Re: [Developers] minor change in search api behavior (empty
resultset will no longer be an error)


On Jul 17, 2008, at 4:10 PM, David Flanagan wrote:

> It occurs to me that this is a case where it might be useful to return 
> a code /api/status/ok/empty.  It still indicates success, but allows 
> it to be special-cased, when desired.

-1

I realize that we may have told developers to look for a prefix matching
"/api/status/ok", but chances are they're not going to do this, and end up
with buggy code as a result.

The bottom line is that returning no results (empty list) is not an error.
I'd even vote for striking the message from the result.

Warren