Alberto Ricart
Alberto Ricart
After some digging through the source found: `aleph.config.json` - it seems the target is honored there - really need some description there as to this file, better yet. Have init...
If we are addressing this type of info, may also want to consider masking `cluster` as well.
Depends on your cluster configuration. On some setups, it is visible. On Thu, Feb 18, 2021, 8:04 AM Jean-Michael Cyr wrote: > @aricart I don't understand, I don't see any...
If the intention is keep my buffer on the small side, perhaps it is acceptable to send a larger message, but this would need to be documented that max_bytes becomes...
more interesting, the consumer will run aground if a single message in the stream has a larger payload - so currently this is a terminal condition for the consumer.
@derekcollison it is a terminal condition because any pull with a lower value will always fail. Possibly this is correct, but since NATS and JetStream have an unit of "message",...
correct, but then at that point, is the reasoning for this PR that if a client wants to use `max_bytes` in a pull, the value shouldn't be allowed to be...
I would love that solution.
Exactly - the point is that users are looking at it not as an illustration of what the API call is doing, but rather as some coherent program which was...
@derekcollison - I agree - In javascript and most other languages that support JSON easily, there's no complexity in encoding/decoding (JSON or otherwise). For NATS this is a bit more...