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
This issue is about making a number of API and internal improvements. Rather than create issues for each I'm listing them together here. Most of these are relatively small and could be fixed together. Some of them will be breaking API changes so it makes sense to try to bundle some before the next version increment.
If you have thoughts on these or other API improvements you'd like to see please share.
Remove "id queue" declarations in AMQPSpace
Instead use ack/timeouts to return a "not found" error. It wastes resources on the server and isn't foolproof anyway.
Move thread event declarations out of Agent class
This would keep all the threading details in the Space class making the Agent class more portable
Remove colorama dependency
Wider Python support including MicroPython
Broadcasts should be self-received
This was a hasty choice made early on and I just haven't gotten around to changing it. The current pattern is not the standard way that a broadcast is handled. The API shouldn't be surprising like this.
...
The text was updated successfully, but these errors were encountered:
This issue is about making a number of API and internal improvements. Rather than create issues for each I'm listing them together here. Most of these are relatively small and could be fixed together. Some of them will be breaking API changes so it makes sense to try to bundle some before the next version increment.
If you have thoughts on these or other API improvements you'd like to see please share.
Instead use ack/timeouts to return a "not found" error. It wastes resources on the server and isn't foolproof anyway.
This would keep all the threading details in the
Space
class making the Agent class more portablecolorama
dependencyThis was a hasty choice made early on and I just haven't gotten around to changing it. The current pattern is not the standard way that a broadcast is handled. The API shouldn't be surprising like this.
The text was updated successfully, but these errors were encountered: