Update:Archive/2.0/Architecture and General Design: Difference between revisions

no edit summary
No edit summary
Line 4: Line 4:


== Addons.Mozilla.Org End-User Website ==
== Addons.Mozilla.Org End-User Website ==
Addons serves as the main point of interaction for developers and end-users to get extensions and themes for their Mozilla products.
=== Overview ===
* DocumentRoot: /opt/update
* URL: addons.update.mozilla.org
* URL: addons.mozilla.org -> redirect to addons.update.mozilla.org (fix for FF 1.0 whitelist)
* Type of content: PHP intensive, very dynamic
* Example request: N/A
=== Questions ===
* How do extenion files get to the mirrors?
* Can we get Firefox to point at this URL for 1.0.1?
=== Architecture ===
=== Architecture ===
==== Main - Items that are common between versions ====
==== Main - Items that are common between versions ====
Line 86: Line 102:
== Plugin Finder Service ==
== Plugin Finder Service ==


(this is for jst)
=== Overview ===
 
* DocumentRoot: /opt/update
* URL: addons.update.mozilla.org
* URL: addons.mozilla.org -> redirect to addons.update.mozilla.org (fix for FF 1.0 whitelist)
* Type of content: PHP intensive, very dynamic
* Example request: N/A
 
=== Questions ===
 
* How do extenion files get to the mirrors?
* Can we get Firefox to point at this URL for 1.0.1?


== Application Update Service ==
== Application Update Service ==


This is the section of the UMO service that actually allows specific applications to check if they need to be upgraded. A couple of questions come to mind here:
This is the section of the UMO service that actually allows specific applications to check if they need to be upgraded.
 
=== Overview ===
 
* DocumentRoot: /opt/update
* URL: aus.mozilla.org
* Type of content: Completely static
* Example request: http://aus.mozilla.org/update/firefox/en-US.rdf


=== Questions ===
* Can we get Firefox to point at this URL for 1.0.1?
* What if this was generated with the UMO toolset and then pushed to several machines designed for delivering static content?
* What if this was generated with the UMO toolset and then pushed to several machines designed for delivering static content?
* Can we return a base URL for Firefox/Thunderbird to chew on?
* Can we return a base URL for Firefox/Thunderbird to chew on?
* Can we better leverage the bouncer so as to not overload the mirror network?
* Can we better leverage/integrate with the bouncer so as to not overload the mirror network?
 
== Infrastructure ==
[[Update:Architecture_and_General_Design:Infrastructure|Infrastructure]]
83

edits