Scott Fauerbach

Bucket names are `restricted-term` so are _very_ limited. Here is an excerpt: ``` restricted-term = (A-Z, a-z, 0-9, dash, underscore)+ filename-safe = (printable except dot, asterisk, gt, fwd-slash, backslash)+ maximum...

I agree that this requirement isn't really useful. The server already would make the name if not supplied. Also, I use the 10 sequence bytes of the nuid, I do...

We are fine with that the name is generated differently on each client. We just want to understand where the requirement to generate the name on the client comes from.

1. Is it possible to use a code other than 409 since this is a success result? Maybe a 200? 2. I thought we already solved the bytes problem, since...

Just to be clear about behavior. Given this: ``` {"batch":10,"max_bytes":20000,"expires":5000000000,"idle_heartbeat":2000000000} ``` 1. If you get 10 messages that total less than 20000 bytes you get `409 Batch Completed` 2. If...

@Jarema I'm still thinking about the case you said that we are being bytes centric and just needed to work it out. TLDR; I see that I need the Batch...

So I guess the only question is, what do we do pre 2.10? I guess it will have to be "close enough for government work" :)

Not a problem with simplification, but some situations that are always going to be a problem with [users] making multiple raw pulls. 1. They issue some pulls with heartbeats and...

+1 for callback. Will allow custom implementations, including for thing like specific dns resolution

I think this needs to be better baked and not a client parity priority. There are other ways to make the pulls more efficient, there is concern about behavior against...