Sorry I haven't been on the list for the last few days.  My account has
been buggy. I missed a lot of discussion as there was just too much to
read if I don't keep up every day.

Anyway, I just committed dotted fields. You can read and write them. One
quirky is that if you do a=b and then a.c=d, the original a=b is
lost. This is because a field can only have either a single value or an
array of multiple values. This is mainly because I couldn't decide where
to put the original single value. The object stored is either a string or
a hashtable. If there is a desire to be able to have both then I can make
every value a pair of an optional string and an optional hashtable. I
wasn't sure if this was necessary or desirble.

Also, I can't run the client because of a ClassNotFound error on
SymmetricCipherConnection. It's a very bizarre error as I can't seem to
find where it is actually be thrown from. Why is this and when will it be
fixed?

Also, why are messages ending with DataLength=0? The last thing I
understood was that we had decided to end them with EndMessage.

Also, I think that we should split the address syntax into two parts. This
would allow for backwards compatibility with old nodes and forwards
compatibility with future nodes.

The two parts are transport protocol and message protocol (or whatever
you'd like to call them). So we can have fps:tcp/blah, tcp/blah,
fps:udp/blah, udp/blah. fps in this example is the secure freenet protocol
in which there is cipher/key negotiation. Lacking a message protocol, it
will assume a straight stream of freenet messages. So old addresses will
work as before both in old and new nodes. New nodes will specify addresses
to each other with fps:tcp and to old nodes with tcp.

This will also be useful in the future when we implement a motley
assortment of message protocols such as SSL, SMTP, etc.. Nodes that
understand a particular message encoding protocol can talk to each other
and will know whether or not they can talk to other nodes by whether or
not they have the appropriate classes to handle the type of address.




_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev

Reply via email to