Update:Archive/2.0/Architecture and General Design

From MozillaWiki
Jump to: navigation, search

« Back to Archive | Update: Main

Ambox outdated.png THIS PAGE MAY BE OUTDATED
This article is in parts, or in its entirety, outdated. Hence, the information presented on this page may be incorrect, and should be treated with due caution until this flag has been lifted. Help by editing the article, or discuss its contents on the talk page.

This document will describe the overall architecture of the UMO services in detail. It should include sub-sections on pfs, addons, etc. that will be populated by the developers working on those components.

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 extension files get to the mirrors?
  • Can we get Firefox to point at this URL for 1.0.1?

Plugin Finder Service

This plugin helps Firefox find plugins it needs to do stuff. Again, we have the huge long URL with unique information in it. Can we fix that? This is a perfect application to leverage caching -- data doesn't change much.

Overview

  • DocumentRoot: /opt/update
  • URL: pfs.mozilla.org
  • Type of content: PHP intensive, mildly dynamic
  • Example request: https://pfs.mozilla.org/plugins/PluginFinderService.php?mimetype=application/x-shockwave-flash&appID={ec8030f7-c20a-464f-9b0e-13a3a9e97384}&appVersion=2004112212&clientOS=Windows%20NT%205.1&chromeLocale=de-DE

Questions

  • Can we get Firefox to point at this URL for 1.0.1?
  • We have got to get Flash off of the UMO servers -- accounts for 53% of traffic right now.

Application Update Service

This is the section of the UMO service that actually allows specific applications to check if they need to be upgraded.

Overview

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?
  • Can we return a base URL for Firefox/Thunderbird to chew on?
  • Can we better leverage/integrate with the bouncer so as to not overload the mirror network?