daniel.moran

Yes, you're right about the instances, it doesn't have a lot of sense to make that mapping static. I'll try to figure out the best way to change this, and...

It may be useful, indeed. We are currently implementing polling commands for the HTTP binding, precisely for the same reason ([this issue](https://github.com/telefonicaid/iotagent-ul/issues/24) was an old one). It seems to me...

I'm afraid IoT Agent has not been tested in such extreme performance scenarios, but since IoTAgents are mostly stateless and your scenario is using such big numbers, I suggest you...

Not really. The problem with the use of DTLS is that the underlying COAP library (node-coap) should support it before. There is an open discussion about that issue [here](https://github.com/mcollina/node-coap/issues/11). It...

Difficult to say without replicating the whole scenario. Can you provide more details about how you created the DTLS tunnel and how are you trying to use the library (commands...

Ok, it seems it doesn't have anything to do with DTLS, as the problem can be reproduced with a simple get request. I'm working on the problem.

Ok. The IoT Agent is using this library to deal with LWM2M, so I'll focus on solving the problem here, and it should be fixed then in the IOTA.

There seem to be a bug in node-coap, `middleware.js`, line 54: `request.packet` should be `packet`. It raises a "request not defined" error that goes all back to the `parseRequest()` catch,...

It is not. Are you sure you are making a single stop call? On Tue, Jan 31, 2017 at 9:41 AM, qusp66 wrote: > when i call the function to...

Of course :) I was talking about what's referred in the protocol as [Configuration Retrieval](https://github.com/telefonicaid/iotagent-mqtt#configuration-retrieval). That's a mechanism that lets the device ask the IoT Agent for particular pieces of...