[Sugar-devel] A small request.

[Benjamin M. Schwartz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Langhoff wrote:
> On Wed, Feb 4, 2009 at 7:21 AM, C. Scott Ananian <cscott at laptop.org> wrote:
>> On Mon, Feb 2, 2009 at 11:19 PM, Martin Langhoff
>>> All I can suggest is that you go back on this thread and read my email.
>>>
>>> Here's a clarification (I know my writing isn't always clear): the url
>>> in the metadata is not expected to remain static over time.
>> How is that a problem?
> 
> All I can suggest is that you go back on this thread and read my email
> stating the use case.

I am finally understanding Martin's dilemma.

Every version of every Activity can potentially specify a different update
URL.  Therefore, the number of entries required in a proxy cache on a
disconnected XS scales not as the number of bundles _to which_ one may
upgrade, but rather the number of bundles _from which_ one may upgrade.
Moreover, the proxy server (though not the XOs), must be aware of all
those versions.

Whether this is a problem is a bit of a judgment call.  In the worst case,
it requires the server to keep an ever-growing database, in case someone
attempts to upgrade from an ancient version.  This creates significant
management overhead, never mind disk overhead.  However, if the proxy
server doesn't have an internet connection, then the XOs also likely do
not have an internet connection, so the XOs are unlikely to wind up with
Activity versions other than the ones on the server or the ones they were
shipped with.

Frankly, I don't think there will be any satisfactory solution until we
implement our designs for a cryptographic bundle system, but that still
seems very far away.

- --Ben
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkmImRkACgkQUJT6e6HFtqRx9wCdHXF6HoHhbzp/eEaK3SxnKfRc
2aMAn2u7m03glSUXiFZi8oEQe1VJ6uef
=bS3g
-----END PGP SIGNATURE-----