Germán Molina Carrasco
Germán Molina Carrasco
@pipermerriam , is the issue solved with the #1799 pull request?
@pipermerriam, @glaksmono .Is this issue still open? it seems that is pretty close to being resolved, May I give it a try?
I forgot to pull the upstream... my fault. Now all test passes.
I have created the question on SOF. Here you have the link: https://stackoverflow.com/questions/61203988/notification-throttling-has-bad-behaviour Thank you
Hi @fgalan Thanks so much for your quick response. One big request or many small ones. Be or not to be, that is... :) Yes, I agree with you that...
Hello @chicco785 this model is not possible because of this issue. [issue549](https://github.com/telefonicaid/iotagent-node-lib/issues/549#issuecomment-423922381) :-(. But even fixing it we have the feeling that we could have a problem with the lazy...
@chicco785 we think that we could have problem at the moment of extract the resource to do the real operation (read/write/execute) to the device, we are still studying the code...
I think that this could solve some problems but it will introduce others. May be we could have a nice talk in the FIWARE submit about it. :-) Best
Hi guys, The lazy attribute problem could be overcome, we have our LwM2M IotAgent representing multi-entity and the structured value like @fgalan proposed, even so, we think that current data...
Hello @jmcanterafonseca We understand the benefits and importance of adopting standards, and more if they are deffined by W3C, but we have to have in mind that the current IDAS...