I am noticing a lot of the system components require us to keep track of attributes assigned to each of the 4 available access points. For example, we need to know whether a connected receiver is active or idle, what the bound socket address is for that receiver etc... Since this will require system-wide access, I am removing the private restrictions over the Access Point Registry in favour of a broadcasted approach for all system components. There are 3 options I see for approaching this:
- Implement the Registry as a Context Manager
- Implement Registry as separate environment variables
- Self-hosted small scale database
The issue with 2. is the added string parsing complexity involved with storing all the necessary attributes assigned to each access point. The advantage is that it still has less overhead than option 1. Option 3 has the most overhead but also is the most scalable. This may be necessary if we expect to be storing a lot of data on the connecting receivers.
I am noticing a lot of the system components require us to keep track of attributes assigned to each of the 4 available access points. For example, we need to know whether a connected receiver is active or idle, what the bound socket address is for that receiver etc... Since this will require system-wide access, I am removing the private restrictions over the Access Point Registry in favour of a broadcasted approach for all system components. There are 3 options I see for approaching this:
The issue with 2. is the added string parsing complexity involved with storing all the necessary attributes assigned to each access point. The advantage is that it still has less overhead than option 1. Option 3 has the most overhead but also is the most scalable. This may be necessary if we expect to be storing a lot of data on the connecting receivers.