TJ
TJ
we have some cases where we have to wait around for some distributed locks so I just keep requeueing the messages to allow messages over other types (that won't collide...
we're siloing for this case using an nsqd per-customer but you can only get to pause/empty at the higher level
I plan on sending a PR at some point, just opening this for reference or if someone else wants to grab it. I think [here](https://github.com/rs/cors/blob/master/cors.go#L268) if we respond with `Access-Control-Allow-Origin`...
any version should be able to update the repo, without updating the program, this will allow me to constantly push new data without releasing all the time
another reminder
reminder to self
we can do this on the fly for libs that do not have compress in their build, and it should be optional anyway. when used inject `.min`
make it less gross
the dreaded reconnect race