Project

General

Profile

Feature #1

Should multiread return an error for an empty log?

Added by Eric Allman almost 3 years ago. Updated about 1 month ago.

Status:
Closed
Priority:
Low
Assignee:
-
Category:
-
Start date:
06/23/2016
Due date:
% Done:

0%


Description

As it stands, multiread on an empty log returns a 404 error (since it's trying to read a record that doesn't exist). It could instead an empty set with no error. Which is the better behavior?

History

#1 Updated by Eric Allman almost 3 years ago

  • Tracker changed from Bug to Feature
  • Project changed from 2 to GDP
  • Category deleted (1)

#2 Updated by Eric Allman over 2 years ago

  • Priority changed from Normal to Low

#3 Updated by Eric Allman about 1 month ago

  • Status changed from New to Closed

This got fixed in GDPv2.

Also available in: Atom PDF