listenForDataAtName (and continuation) give unintuitive results

Description

Javascript that demonstrates this unintuitive behavior: https://gist.github.com/JoshOrndorff/b0fe7aed93d16beabc2885484c6e8c54

Current Behavior
The current listenForDataAtName query takes in a depth parameter which tells it how many blocks deep into the DAG to check for sends. If any data was sent on the name in question in the queried part of the DAG, then all data at that name is returned (even if it was sent deeper in the DAG than the specified depth parameter).

Acceptable Behavior #1
Tell me about all sends in the tuplespace on a per-block basis for the portion of the DAG that I queried regardless of when those sends happened

Acceptable Behavior #2
Tell me about only the sends that occured in the part of the DAG that I queried.

Actually these may both be useful APIs, but I would settle for either one.

Environment

None

Status

Assignee

Unassigned

Reporter

Joshy Orndorff

Priority

Medium

Affects versions

None

Components

None

Sprint

None

Epic Link

None