> What you've just described above is very similar to what I call a code > file. Part of the purpose of DSKs is to automate the process of looking > up this code, and to adopt a standard convention for handling data > submissions. DSKs could even be done client-side if that's what you > prefer. The DSK makes things transparent/automatic and standardized.
Here is the current method for resolving an index prefix: Start with the prefix for the prefix index. Fetch prefix-date. Read the first line. This is your prefix. Example: Prefix: "myindex" Date: 986967900 Fetch "myindex-986967900" First line is "eiold" Prefix = "eiold". So this is the current system. It's standardized. It's simple. Does the DSK system have any benefits over this system? _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl >From devl-admin at freenetproject.org Wed Apr 11 02:13:06 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 CAA31347 for <danello at danky.com>; Wed, 11 Apr 2001 02:13:05 -0400 Received: from hawk.freenetproject.org (localhost [127.0.0.1])
