I can't tell from the source or the BZ what your scalability plan is. Once I have a bazillion megabytes of catalog history, how do I reset it? Is it stored on the server as deltas and also as a complete file? (Only looking at the 10,000 foot level here, I'm not familiar with the source)
--chris [EMAIL PROTECTED] wrote: > 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 > > -j > _______________________________________________ > pkg-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/pkg-discuss _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
