On Apr 5, 2011, at 8:53 AM, Yury V. Zaytsev wrote: > On Tue, 2011-04-05 at 08:50 -0400, Jeff Johnson wrote: > >> Any interest? > > What does it mean in the practical terms? Sorry, I'm far from being an > RPM wizard to understand your message completely... >
Here's the practical relevance: I'm going to integrate a depsolver into RPM @rpm5.org. In order to attempt that client-side work, I need to deploy server side infrastructure. Instead of mirrors and markup as is currently and traditionally done, I'm going to use a NoSQL! distributed store instead. Tools on the client side will then be written to add incremental (i.e. less bandwidth, faster) metadata updates for all the usual depsolvers (yum/smart/urpmi/etc) to use. Having a single distributed store, with incremental updates of client side markup used by existing tools, is a paradigm shift from other distribution schemes. But I'm quite sure that an incremental update, and the replication/sharding used in NoSQL! distributed stores, will be an improvement on the existing traditional means of store-and-forward downloading of "repository" metadata. SO I'm shopping for RPMForge (because its perhaps the best add-on repository in the world) interest, and will host and maintain a public MongoDB database for RPMForge in order to proptype my development work @rpm5.org. It *is* just metadata, and *will* be publically available, whether you choose to use @rpm5.org code or not. 73 de Jeff _______________________________________________ users mailing list [email protected] http://lists.rpmforge.net/mailman/listinfo/users
