> No, what I'm thinking of would require a change to the server, because the
> keys would have to be stored on the server differently from how they are
> stored the old way (the entire key was hashed) or how they're stored in the
> catalogs.

If you expect your code to be integrated into Freenet then it would be
wise to talk to the people working on the node before you spend a lot of
time coding.

> Thanks for the discussion.  I'm going to make the changes, although it may be
> easier to make the changes on the code that doesn't have all of the
> infrastructure for catalogs in it.

The key index code is entirely client-side and contained in a single file,
Freenet.client.KeyIndexClient, which no other files depending on it. So
you shouldn't notice it at all.


_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://lists.freenetproject.org/mailman/listinfo/devl
>From - Fri Apr 20 11:47:48 2001
Return-Path: <devl-admin at freenetproject.org>
Received: from hawk.freenetproject.org (postfix@[4.18.42.11])
        by funky.danky.com (8.9.3/8.8.7) with ESMTP id XAA27786
        for <danello at danky.com>; Thu, 19 Apr 2001 23:47:57 -0400
Received: from hawk.freenetproject.org (localhost [127.0.0.1])
        by hawk.freenetproject.org (Postfix) with ESMTP
        id 6D7FF5803E; Thu, 19 Apr 2001 20:29:08 -0700 (PDT)
Delivered-To: devl at freenetproject.org
Received: from mta5-rme.xtra.co.nz (mta5-rme.xtra.co.nz [203.96.92.17])
        by hawk.freenetproject.org (Postfix) with ESMTP id 21BA957D98
        for <devl at freenetproject.org>; Thu, 19 Apr 2001 17:24:05 -0700 (PDT)
Received: from private ([210.54.230.203]) by mta5-rme.xtra.co.nz with SMTP
          id <20010420001827.HYNA466602.mta5-rme.xtra.co.nz at private>
          for <devl at freenetproject.org>; Fri, 20 Apr 2001 12:18:27 +1200
Message-ID: <00f001c0c92f$334e4fb0$cbe636d2 at private>
From: "David McNab" <[email protected]>
To: <devl at freenetproject.org>
References: <Pine.OSF.4.33.0104191836440.1306-100000 at moe.cc.utexas.edu>

Reply via email to