You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems to me that there is a potential issue of InvokeId reuse. It is guaranteed to occur when more than 256 BACnet devices are accessed simultaneously. At the moment, "_getInvokeId()" simply returns the next value in order, without checking its reuse.
I have no idea how to fix this yet. In my opinion, ideally there should be a queue of free "InvokeId" values. When this queue is exhausted, execution should pause waiting for free values.
The text was updated successfully, but these errors were encountered:
Node Version:
any
Node BACstack Version:
0.2.4
Feature Request / Question
It seems to me that there is a potential issue of InvokeId reuse. It is guaranteed to occur when more than 256 BACnet devices are accessed simultaneously. At the moment, "_getInvokeId()" simply returns the next value in order, without checking its reuse.
I have no idea how to fix this yet. In my opinion, ideally there should be a queue of free "InvokeId" values. When this queue is exhausted, execution should pause waiting for free values.
The text was updated successfully, but these errors were encountered: