when processing queued messages after reconnecting, send messages with LIFO instead of FIFO as the latest data is the most important for rea
when processing queued messages after reconnecting, send messages with LIFO instead of FIFO as the latest data is the most important for real time monitoring. This is similar to the one posted already36 votes
Currently IoT Hub and Edge Hub guarantee that messages will be delivered in order. Would folks want this promise to be broken? How would people want to rationalize ordering with other messages.
Currently there is a limit of 10 modules (includes agent, hub) to be deployed to IoT Edge device. What is the plan for module deployment limit for GA release? The reason is the solution we are working demands multiple (more than 8) peripheral integration at device level and we see that each Edge module could represent the peripherals. Also, please share tentative plan of GArelease?15 votes
The limit has indeed been raised to 20. We’re interested to learn about scenarios that require more than 20 modules.
During offline with IoT hub, is it possible to have a mechanism at Edge device to distribute the messages among other Edge devices? This will help to address a scenario were one Edge device needs to share message/information with another Edge device as there is no cloud data storage share available due to
connectivity issue.8 votes
We have a shared endpoint NGNIX where all device communication is ending on our network. Based on protocol and ports we configure forwarding rule towards the iot hub.
Is this supported to configure https mqtt to custom port rangens instead of the following
I didn’t quite understand your question. Are you trying to use NGNIX as a proxy for your network traffic? If so, does this documentation help?
- Don't see your idea?