284592 - allow update schema to express client system's capabilities

Status: RESOLVED FIXED

(Toolkit :: Application Update, defect)

Description

[Chase Phillips]

Client update should be able to handle the primary attributes of the client
system and many of the secondary attributes.

  * Operating system (ie. win32, linux, mac)
  * Architecture (i686, i386, ppc, sparc)
  * Product (firefox, thunderbird, suite)
  * Version (1.0, 1.0.1, 1.0.1a, 1.0.1rc2)
  * Window toolkit (GTK1, GTK2)

We should allow the most expressive semantics so that clients can do the right
thing.

  * OS=(win32|linux) and Architecture=(i386)
  * Product=(firefox) and Version=(1.0|1.0.1)

Comment 1

[alanjstr]

Snag the code from the extensions updating system.  

Comment 2

[Darin Fisher]

The new update system has this capability minus windowing system.  Can we mark
this FIXED?

Comment 3

[Chase Phillips]

(In reply to comment #2)
> The new update system has this capability minus windowing system.  Can we mark
> this FIXED?

All is fixed except for the windowing system and expressive semantics which we
no longer need.

Before, the client needed to decide which update from a list of many possible
updates it should apply.  The semantics aren't needed now because we've moved
all of the smarts for deciding which update to apply out of the client and into
the server (choosing to encode all of the permutations into 0/1-update URL
references).