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
There are cases where the build in queue is only causing more issues than that it actually solves. #81 being on of them.
In my use case I just want randomly broadcast messages towards ports and if a servers goes up, it will automatically start receiving messages. I'm currently sending heart beat messages every 100 ms (for a master slave setup). So if a server goes down for a hour it will just cause the node process that sends packets to blow up out of memory or the receiving side of the message to blow up because of the large blob of data it needs to process.
The text was updated successfully, but these errors were encountered:
There are cases where the build in queue is only causing more issues than that it actually solves. #81 being on of them.
In my use case I just want randomly broadcast messages towards ports and if a servers goes up, it will automatically start receiving messages. I'm currently sending heart beat messages every 100 ms (for a master slave setup). So if a server goes down for a hour it will just cause the node process that sends packets to blow up out of memory or the receiving side of the message to blow up because of the large blob of data it needs to process.
The text was updated successfully, but these errors were encountered: