naggie/megafilter

switch fro, HTTP API errors

Opened this issue · 3 comments

just return an empty set or something so that errors actually mean something unique

because a broken network connection is indistinguishable from an empty queue.

Another solution would be to look at the error

use error classes from restify, passed to next()

also publishing an item that is already published is indistinguishable from not found or any other error