I'm not sure if you know perst, it fits the needs you listed. I could give you some first step advise if you want.
On Mon, Mar 3, 2008 at 10:18 PM, Julien Cornuwel <batosai at batosai.net> wrote: > bbackde at googlemail.com a ?crit : > > > Try perst. Seagull already made good experiences with the perst > > performance, as I did in Frost. > > He works on the Java port of fms. As far as I know there is already > > some kind of trust system inside > > the fms code? So lets start using the Java port code and maybe separate it. > > Mmm, I don't think perst will fit that plugin's needs. Its operation > will consist in : > - The user sets a trust value for an identity. Get all identities that > are trusted by this one and re-calculate*. > - We fetched a new trustlist (from a trusted identity), re-calculate* > all listed identities. > > * Get all the identities that trust a particular identity and calculate > the resulting trust. > > If we assume it has a lot of identities to handle, the re-calculation > process will happen very often and I can't load every identities in > memory and perform selections on them, each time. I need a way to only > get those I'm interrested in. > > I see two solutions : > - SQL (easy, but has to be embedded in freenet) > - Files (named like the identity they represent), listing the identity > they trusts AND the identity that trust them. That would use a lot of > disk space but garantees a fast access to the data. > > I think the SQL is cleaner but am open to suggestions that are going to > work with, let's say, 100.000 identities. > > > _______________________________________________ > Tech mailing list > Tech at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/tech > -- __________________________________________________ GnuPG key: (0x48DBFA8A) Keyserver: pgpkeys.pca.dfn.de Fingerprint: 477D F057 1BD4 1AE7 8A54 8679 6690 E2EC 48DB FA8A __________________________________________________
