Quoc-Viet Nguyen
Quoc-Viet Nguyen
Thank you, I'll check it out
Thanks for your suggestion. I agree that a boolean may be better in this case, but I also would like to not change the API to make it backward compatible....
wrt concurrent access, I'm in the process of adding mutex in the client transporter and fix #16 (expected to be done this week :) ) The client api doesn't have...
I don't think Close is needed (like http client). Will send a PR for #16 this weekend so you can see what I mean. Cheers
There is an example: https://github.com/goburrow/modbus#usage Docs: https://godoc.org/github.com/goburrow/modbus#Client
Yeah, I had thought about implementing a modbus server, but found all I need with [this binary](http://www.modbusdriver.com/diagslave.html). But you're right, a proxy/router is a nice feature to have. Feel free...
I have tagged v0.1.0. I'll check those PRs later
I also maintain a custom implementation based on crypto/tls for another QUIC implementation. I'm trying to reuse tls.Config as much as I can but still haven't found a proper way...
@GitRowin due to performance concern, expireEntries is not called for every read request and it returns old/expired entry instead of block loading new value. If your application has low request...
Another way is changing https://github.com/goburrow/cache/blob/f6da914dd6e3546dffa8802919dbca80cd33abe3/local.go#L180 from `refreshAsync(en)` to `refresh(en)` I can change that as default behavior instead, however it will block the whole cache.