Jiangge Zhang

@dagwieers

@mskucherawy Have you implemented some automatic re-connecting mechanism?

Hi @akshjain83, The client does not initialize any recipe by itself. The `client.DataWatch` and `client.ChildrenWatch` are just factory functions. It seems not bad to have `client.TreeCache` too. May you open...

The current implementation of connection routine uses blocked-style `handler.select`. It works well with monkey patch based solutions but does not work with asyncio. In my opinion, this is a price...

IMO 使用异常，还是 nil 值，还是 Optional 类型，看各语言的 idiomatic 用法即可… spec 也可以仅要求这一点

我认为有两种方案: 1. 中间级行政区不存在的，可以用上级行政区来补全。例如 `110101` 为 `北京市-北京市-东城区` (`1101xx` 按照 `11xxxx` 补全为 `北京市`) 2. 中间级行政区不存在的，填充空数据，在 spec 中注明该行为，实现格式化库函数的时候加以处理。例如 `110101` 为 `北京市-空-东城区`，库函数格式化为 `北京市东城区` （跳过空记录）

这样上传的只是 recipes（构建脚本），二进制 packages 还是没上传。而 recipes 根本没多大，直接 clone 仓库 https://github.com/conan-io/conan-center-index 就能看到了。 感觉 conan 这种二进制包和目标平台 ABI 强绑定的，不太适合建公有 mirror，如果是组织用，不如自己基于 conan-center-index 搭个 in-house remote，直接用开源的 `conan_server` 很方便的。怕数据丢失就拿 [s3fs](https://github.com/s3fs-fuse/s3fs-fuse) 或者 [juicefs](https://github.com/juicedata/juicefs) 挂载一个 data volume 再启动 `conan_server`...

IMO, the threading handler could work well in Python 3 without gevent. It will not be a performance issue because there is only one background threading to keep the state...

@noirbizarre Thank you for your feedback. It's my wrong indeep. Actually I think the `ident` composed with `endpoint` and `args` is a bad idea after the v0.1.0 released. I regreted...

You can design it and send a pull request. :+1: