-
Notifications
You must be signed in to change notification settings - Fork 182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Having the ability to have our own MeshNetworkCallbacks #353
Comments
Hi @Kleak, could you elaborate a little bit more on this? As of now every time the network is changed due to a mesh message that is sent/received you receive a callback |
in fact onNetworkUpdated is loosing lot of information. example : what i would like is having a way to be sure this event is the response of my select provisioner which MeshNetworkCallbacks provide but is not available to us. |
Right I see, this is something I can look into but it will have to wait a little bit unfortunately. What I can do is add a callback for each database update i.e. provisioner, app keys and etc. hope this would work for you? |
Yes that would be ok 👍 |
ok, as of now I have some other priorities but i will look in to as soon as I get some time. |
As of today we only have onMeshNetworkUpdate but we lost a lot of information on why it's updated.
It would be great if we can have our on MeshNetworkCallbacks. By having this we will not lost why the MeshNetwork is updated and allow more granularity when executing functionality.
The text was updated successfully, but these errors were encountered: