OlivierHecart

### Describe the feature `Session.info()` function currently returns `InfoProperties` (a set of Key/Value pairs). This forces all the properties to be build at least on first `info()` call even if...

Remove queryable kind

1

The queryable kind: - Makes the wire protocol and the routing more complex. - Brings extra concepts (like eval) and complexity to the API which are not necessary as: -...

`Query.reply()` should return a `ZFuture`

1

`Query.try_reply()` and `Query.reply_async()` should be removed. `Query.reply()` should return a `ReplyBuilder` which implements `ZFuture` and so provide `.await`, `.wait()` and `.poll()`

Subscribers Reliability option is ignored and all messages are sent reliably. The option should be propagated in the network and data should be sent accordingly.

The following messages can sometime be found in zenoh logs : ERROR zenoh::net::routing::network] Received LinkState from XXXX with unknown node mapping X ERROR zenoh::net::routing::network] [Xxx network] Received LinkState from XXXX...

**Problem:** The following example hangs: ```rust let queryable = session .declare_queryable("test") .res() .await .unwrap(); loop { select!( _query = queryable.recv_async() => {}, _ = stdin.read_exact(&mut input).fuse() => { let replies...

**The reason for `AUTO` query consolidation:** The default `ConsolidationMode` is `Latest`. But when querying a time series storage with a time range query parameter, the user typically wants multiple samples...