Simon Lin

Creating a new OT 1.1 reference release using latest OpenThread code can fix this issue, but it may have unexpected impact on the Thread 1.1 certification. I would suggest to...

Be careful that it might cause OpenThread THCI or other scripts to fail. @Moandor-y

Maybe we should remove all `otInstance *aInstance` from APIs and not provide `otSelectInstance`. There seems no real use case for `multiple OT instances`

> > There seems no real use case for `multiple OT instances` > > ot-esp32 project needs to dynamically allocate the OT instance. Yes, you are right. We took advantage...

Agree that `otSelectInstance` is not convenient to use if there are indeed multiple OT instances. Agree that we should not alter current API if we might need multiple instances in...

master上已经是用go mod了

有几个好处： - 减少game和gate之间的连接数量。game和gate进程的数量需要随着玩家数量和游戏逻辑的复杂性上升而增加。如果每个game都和每个gate建立连接，总的连接数量会很大。而dispatcher的数目相对较少，这样减少了总的连接数目。 - Dispatcher记录了所有entity在哪个game上，这样entity之间只要拿到ID就可以相互调用RPC。 - Entity在game之间迁移，或者热更新game进程的时候，dispather可以保证RPC消息的可靠性和有序性。 如果没有dispatcher应该也是可以做到这些的功能，但是会困难一点。

@jwhui Would need https://github.com/openthread/ot-ns/pull/324 to resolve CI fails.

Can we add a method to get/set log level in OTNS.py @EskoDijk

> > Can we add a method to get/set log level in OTNS.py @EskoDijk > > I added a str property in OTNS.py. 👍 Great idea to use `@property`.