Hello! I followed the megaphone link in the FAET newsletter to understand what this tool is and what problem it tries to solve so that way I'm aware of this tool in case I ever need to use it for my team. Unfortunately, I'm not sure I understand the project. On the readme, I see:
A rust based real-time update broadcast server for Firefox
What kind of broadcasts are made? To who? Can any information be sent over or does it have to be pre-defined in some way?
I followed the "API doc" in the readme as well as the use cases and found:
Firefox currently polls a number of different services to check for updates. With polling we must choose a frequency that balances cost and update latency. Traditionally this has been 24 hours. The proposed real time updates project provides us new capabilities that we can’t accomplish with polling alone:
That's really helpful! I think that should go in the readme. Additionally, I'd wonder: is this something my team (Android Product Team) should be aware of so we can utilize it's features (as an application team) or is this something that will be a passive background improvement to services? Thanks!
pjenvey
commented
6 years ago
Hello! I followed the megaphone link in the FAET newsletter to understand what this tool is and what problem it tries to solve so that way I'm aware of this tool in case I ever need to use it for my team. Unfortunately, I'm not sure I understand the project. On the readme, I see:
What kind of broadcasts are made? To who? Can any information be sent over or does it have to be pre-defined in some way?
I followed the "API doc" in the readme as well as the use cases and found:
That's really helpful! I think that should go in the readme. Additionally, I'd wonder: is this something my team (Android Product Team) should be aware of so we can utilize it's features (as an application team) or is this something that will be a passive background improvement to services? Thanks!