On Wed, May 02, 2001 at 09:48:36PM -0700, Mr. Bad wrote: > >>>>> "TC" == Tavin Cole <tavin at mailandnews.com> writes: > > TC> That's just a fluke. It won't be supported in 0.4. > > So, this is kind of dorky, but is there any way to get a vague list of > what -will- be in 0.4? I'm following the code in experimental, but not > everyone else is, and not all of the stuff that comes down as "in 0.4" > has been coded yet. > > The roadmap is just way too high-level. It'd be cool to have some > rough ideas.
Here's a probably incomplete list: - Oskar rewrote the node's internal message handling architecture, which is now a kind of state machine and should be very robust. - Increased security of keys, with untamperable storables and possibly moving Metadata-length out of the storables. - Node announcement. - ARKs (probably not in first release) - Load balancing (probably not in first release) - Decaying contact probability heuristics for nodes with connection problems. - Robust FCP in node states architecture. - Internal client for plug-ins. - New metadata and AutoClient. - Datastore in an encrypted file. - Separation of routing table and datastore. No more file limits. - No more temp files all over the place. Temp storage will be allocated out of the datastore itself. Safer too. - Bandwidth throttling by day,week,month etc. (this may not be in the first release -- Job Jar Mr. Bad?) - Randomized HTL decrement for low HTL. - Power of 2 file sizes only. - Several protocol changes.. reversed StoreData on inserts, no more
