Matthias Hanel

@goku321 we will be adding your proposal 1, triggered by a system account message

> In a server restart scenario, was the internal consumer hydrated with the updated config from store at that time? Is this fix making sure that the config update (source...

I would go with sending at least one message. In part because at the moment max_msg_size is optional. This also seems less complicated to implement than, say having to make...

> Large ones like this might require a f2f walkthrough.. @derekcollison Absolutely, just pushed changes as I'm looking at something with Alberto

@goku321 What's your expectation for an R2 consumer in an R5 stream where both consumer nodes are shut down? In step 2 you write "Create a stream and a R1...

@shiv4289 , but loosing the offset is basically what it'd mean if we where to automatically migrate the R1 consumer, once it's machine disappears. > Expected result: > The consumer...

@ripienaar @derekcollison @wallyqs I've been needing this again and ended up with smth that looks a lot like the snippet below. Would this be an acceptable api/name/implementation ``` func (nc...

Just brought it up because I am repeatedly facing requests with more than one responses. This is essentially a request, but with more than one response. So can't fit in...

@derekcollison @aricart , the only possible difference I see is that with Chunked - no matter how you design your chunking protocol - you **can't afford to miss a message**...

I'd rather see the system become better at interest based cleanup than adding eof. Stream or chunked is for the service exporter to express if it's response data is idempotent...