3,035
edits
Changes
→Feature Discussion
The future of Bouncer depends on the development of UMO and what role people see it playing in relation to Mozilla's update service. It will continue to distribute binaries through the mirror network, but how it can better fit into Mozilla's workflow has yet to be determined. We are working on figuring out how it can help automate and combine builds, updates, etc. The best is yet to come.
== Feature Discussion Bouncer Ideas ==
* Proactive mirroring
** It occurs to me (Chase) that if bouncer has a list of mirror sites and then checks the sites for new file additions as we add them to dmo, we are nearly to the point of closing the loop and just signaling to the mirror sites that a new file is available for d/l and for them to grab it. From here, we could do other sorts of neat things:
** Will this present a larger problem? How important is this? Thoughts?
* Filepath Exceptions
** Bouncer needs to be able to handle products and files that do not fit the common schema for building URLs.
*** For example, if the OS is in the file name.
*** Or if there are no localization paths, etc.
** Essentially it should allow us to specify a larger chunk of the URL based on an option.
== Server Requirements ==
