Update:Archive/2.0/Developers: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 9: | Line 9: | ||
=== Roles === | === Roles === | ||
=== Services === | === Services === | ||
=== Expected Behavior (client-side) === | |||
==== Extensions ==== | |||
* If a newer version is available, display update information. | |||
* If there is information on the current version, display information so client can update extension metadata. | |||
* Cases where there is no output (expected error code): | |||
** Bad inputs (1) | |||
** Failed query or no DB connection (2) | |||
** No results (3) | |||
** Client extension version is greater than anything in UMO database (4) | |||
==== Application Update Service (aus) ==== | |||
==== Plug-in Finder Services (pfs) | |||
== Application Infrastructure == | == Application Infrastructure == | ||
Revision as of 00:35, 8 March 2005
Update: Home Page » Development »
Plan
Schedule
Responsibilities
Requirements
Goals and Priorities
Roles
Services
Expected Behavior (client-side)
Extensions
- If a newer version is available, display update information.
- If there is information on the current version, display information so client can update extension metadata.
- Cases where there is no output (expected error code):
- Bad inputs (1)
- Failed query or no DB connection (2)
- No results (3)
- Client extension version is greater than anything in UMO database (4)
Application Update Service (aus)
==== Plug-in Finder Services (pfs)
Application Infrastructure
Development
Staging
Production
DB Infrastructure
Development
Staging
Production
Project Standards
What language should we use?
Sticking with PHP seems to make the most sense at this time. We have that skill set (both on the development and systems side) and the alternatives are not particularly attractive. We considered both Perl and Java but decided against both at this time. The existing UMO service is currently scaling quite well with over 3 million unique clients a day across 3 servers.
What tools/frameworks will we use?
This is an ongoing discussion that will hopefully yield the "best tools for the job".
What about coding standards?
We are going to stick with the standard Mozilla coding standards where they apply and then develop our own where they do not.