While GETs are currently supported, clients have no way of controlling the "answer". If a a vault returns the address of a stale service, the client re-requesting that service can only hope that it gets the address of a different service. This enhancement would introduce blacklisting such that clients can specify a series of addresses (and/or IDs, depending on implementation) that the vault shall not answer the request with (preferring instead to return an empty answer).
Please note that long blacklists may exceed the max packet size. As Slims does not yet support packet streaming, callers should instead receive an error if their blacklist is too long.
While GETs are currently supported, clients have no way of controlling the "answer". If a a vault returns the address of a stale service, the client re-requesting that service can only hope that it gets the address of a different service. This enhancement would introduce blacklisting such that clients can specify a series of addresses (and/or IDs, depending on implementation) that the vault shall not answer the request with (preferring instead to return an empty answer).
Please note that long blacklists may exceed the max packet size. As Slims does not yet support packet streaming, callers should instead receive an error if their blacklist is too long.