* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [2007-12-04 01:44]:
> The following webrev implements an incremental catalog update mechanism.
> As the size of the catalog increases over time, we'll save bandwidth and
> processing power if clients download a subset of changes to the catalog.
> Otherwise, clients would download an entire catalog on each refresh,
> probably wasting a lot of extra information.
>
> The webrev is here:
>
> http://cr.opensolaris.org/~johansen/webrev-cat-inc/index.html
*. I think the overriding question I have is "does every catalog have
an associated update log?" (Every update log has a catalog.) I
believe that the server-side is almost phrased entirely in terms
of the update log, and I'm wondering if we should make that more
clear. Perhaps the update log is derived from the catalog type?
(Even on the client side, it looks as if the update log is the
changing entity, and the catalogs are just cached state.)
Perhaps this can be addressed by expanding on the catalog-updatelog
relationship in their docstrings. Other than that comment, I only
have one nit:
depot.py:
164. This change looks like a separate issue. Is there a bug ID for
this piece?
- Stephen
--
[EMAIL PROTECTED] http://blogs.sun.com/sch/
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
